Clustered Environments Troubleshooting

Problems in a Clustered Environment

All nodes must join the cluster before you make any changes to any governing settings, such as in the Intelligence Server Configuration Editor.

What Order Should I Start the Server Nodes?

If powering on after a power failure, it does not matter what order the nodes are powered back on. Once the nodes are on, use the Cluster Monitor to determine which machine is the primary node, and then manage any caches.

Which Node am I Connected to?

In Developer, the project source definition includes the server name. Developer connects to a specific node only, so you can control which server you are connected to.

In MicroStrategy Web, new connections are dynamically directed to the least loaded node. Although a server name may appear as part of the URL, this may not be the node to which the user is connected. To determine which node a Web user is connected to, use the User Connection Monitor to see which node the user's name appears in (see Monitoring Users' Connections to Projects).

Do I Need Multiple Project Sources?

Because Developer connects to a specific node in a cluster, project sources must be created to each node to fully access and monitor the cluster.

Does it Matter Which Node I Connect to in Developer?

Nodes in the cluster can host a different set of projects from the same metadata. The node to which a Developer user connects is important because it dictates which projects are available to the user at that time.

Can I Control Which Node I Connect to in MicroStrategy Web?

Controlling connections other than by default load balancing requires customizing MicroStrategy Web. The MicroStrategy SDK and MicroStrategy Developer Library (MSDL) contain information on customizing MicroStrategy Web.