SYMPTOM
In a clustered Strategy 9.3.x - 9.4.x. environment, when one of the machines hosting the Strategy Intelligence Server is shutdown, the other Intelligence Servers in the cluster are very slow in responding or unresponsive. This issue is more commonly observed when Strategy Intelligence Server Universal is installed on UNIX/Linux operating systems. This issue is particularly seen when the machine is shutdown without first shutting down the Strategy Intelligence Server process.
Errors similar to the following are seen in the DSSErrors log (if the Kernel > Warning traces are enabled):
2014-03-26 18:42:21.461+01:00 Fatal error: unable to connect to the server. 2014-03-26 18:42:21.462+01:00 ClusterManager::Validate(): Server <l93> not responding (failed): HResult = -2147206913. Try one more time. 2014-03-26 18:42:24.465+01:00 Fatal error: unable to connect to the server. 2014-03-26 18:42:24.466+01:00 ClusterManager::Validate(): Server <l93> not responding (failed): HResult = -2147206913.
[HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\DSS Server\Castor]
"SkipClusterChecking"=dword:00000001
After disabling the automatic join feature by adding the above registry setting, to ensure that the cluster is automatically formed after Strategy Intelligence Server restart (shutdown can be normal shutdown or unexpected), all the servers should be selected on the server definition under Strategy Intelligence Server Configuration > Clustering as shown below. If the servers are not selected, the cluster is not automatically formed upon restart.

WORKAROUND
To avoid seeing this issue, shut down Strategy Intelligence Server before shutting down the physical machine. With this, the other nodes in the cluster will not try to communicate with the down node.
Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Strategy. Any edit of the registry is done at the user's own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. Users should make a backup of the MSIReg.reg file before making any changes.