PRB: Application Center Cluster Members Are Automatically Synchronized After Rebooting

If you reboot a member server of an Application Center 2000 cluster, the member server will request a synchronization from the cluster controller. This will occur even if you have cleared the Enable automatic updates check box on the cluster Properties page.

If a member has been shut down for any period of time, it cannot know if content has been changed on the cluster controller while it was down. Application Center 2000 does this to prevent inconsistencies within the cluster.

If you want to prevent a member from synchronizing automatically after a reboot, remove the member from the synchronization loop prior to restarting the member. Note that the member does not have to be up when you remove it from the synchronization loop.

1. From the Application Center Management Console, right-click the member server and select Properties.
2. Clear the Include this member in synchronizations check box.
3. Click OK.

This behavior is by design.

Excluding a member from synchronizations also prevents that member from receiving application synchronizations and cluster synchronizations (automatic, periodic, or manual). However, executing a deployment to the member or selecting the member and clicking Synchronize Member will synchronize all applications with the cluster controller, whether or not the member is included in synchronizations.

When you select Include this member in synchronizations to put the excluded member server back into the synchronization loop, you are presented with a dialog box that states "One or more applications on this member may be inconsistent with those on the controller. Would you like to perform a full synchronization to ensure consistency?" If you click Yes, the member will be synchronized immediately. If you click No, the member will be added back into the synchronization loop in a possibly inconsistent state.