Node Synchronization in a Clustered Environment

When do I need to purge the object cache?

• When an object is edited on one cluster node, the updated version ID of the object is announced to the other nodes. This allows the other nodes to invalidate the object if they have it in memory and retrieve a fresh copy from the metadata. Therefore, in this instance there is no need to purge the object cache.
• If changes to an object are made in 2-tier (Direct) mode, those changes are not propagated to any Intelligence Servers connected to the metadata. Additionally, if an object is modified from an Intelligence Server that is not in the cluster but it is using the same metadata, the cluster nodes will not know of the object change. In these cases, the object cache should be purged.

When do I need to purge the element cache?

• The element cache should be purged as a routine part of a warehouse load or any time the elements associated with an attribute may have changed.
• You can automate purging the element cache using MicroStrategy Command Manager. See Automating Administrative Tasks with Command Manager.

Which machine is my history list on?

• For Intelligence Server 7.1 and later, the combined History List in memory is a sum of all local files and is automatically synchronized. Therefore, you cannot tell which pointers are on which machine.

In what order should I start the server nodes?

• If powering on after a power failure, it does not matter what order the machines are started. It is important to locate the machine that is the primary node, so that cache management can be controlled. The primary node is designated in the Cluster Monitor. See Manage Your Clustered System.