KB40403: In MicroStrategy Intelligence Server, how does the project configuration setting "Load Intelligent Cubes on startup" function when both nodes experience an abnormal shutdown but only one node starts up.

In Strategy Intelligence Server 10.x, how does the project configuration setting "Load Intelligent Cubes on startup" work in a clustered environment?
The "Load Intelligent Cubes on startup" setting is located in Desktop under Project Configuration > Intelligent Cubes. The expected behavior pertaining to the loading Intelligent Cubes to memory during startup in a clustered Intelligence Server environment is explained in the following Strategy Knowledge base article: 
KB37213: In MicroStrategy Intelligence Server 9.2.x and later, how does the project configuration setting "Load Intelligent Cubes on startup" work in a clustered environment?
How does cluster failover work with the "Load Intelligent Cubes on Startup" setting enabled and only one node recovers after both cluster nodes fail (e.g., power failure)?
For the sake of brevity, this question is answered with an example containing a two node cluster (e.g., NodeA and NodeB) with each Intelligence Server node running on a Unix/Linux machine, using centralized caching (configured on a separate machine) and the "Load Intelligent Cubes on Startup" setting is enabled.

1. An Intelligent Cube (CubeB) is published on NodeB. The Intelligent Cube can be seen in the Intelligent Cube monitor on NodeA and loaded into memory on NodeA.
2. On both nodes, the user has the ability to successfully execute reports in the clustered environment.
3. Terminate the Intelligence Server process (using the kill -9command) on NodeB to simulate a crash\power outage.
4. NodeA still has the Intelligent Cube loaded into memory and the user can successfully execute reports because failover is in effect.
5. Terminate the Intelligence Server process (using the kill -9 command) on NodeA to simulate a crash\power outage.
6. Start NodeA and the user will notice that the CubeB no longer appears in the Intelligent Cube monitor and reports based on this cube cannot be run.

This is working as designed. Once NodeB is started, the Intelligent Cube will be loaded into memory on both nodes.
 
 
40403