Shut Down a Node

MicroStrategy ONE (June 2024) introduces a preview feature to Preview Feature: Access Cubes Regardless of Node Status.

A node can be shut down in two ways:

• Administrative shutdown: This includes instances when a node is removed from a cluster or the Intelligence Server service is stopped.
• Node failure: This includes instances such as a power failure or a software error; this is sometimes called a forceful shutdown. Forcefully shutdown nodes retain their valid caches if they are available. However, while the node is shut down, there is no way to monitor the caches, change their status, or invalidate them. They can be deleted by manually deleting the cache files on the local node or by deleting the appropriate cache files on a shared network location. Be aware that cache files are named with object IDs.

The results of each of these types of shutdown are discussed below.

Resource Availability

If a node is rendered unavailable because of a forceful shutdown, its cache resources are still valid to other nodes in the cluster and are accessed if they are available. If they are not available, new caches are created on other nodes.

In an administrative shutdown, caches associated with the shut down node are no longer valid for other nodes, even if they are physically available, such as on a file server.

Client Connection Status

Developer

Client connections that are not cluster-aware, such as Developer, do not experience any change if a node is removed from a cluster. However, the local node must regenerate its own caches rather than accessing the resources of other nodes. If Intelligence Server is shut down, any Developer clients connected to that Intelligence Server receive an error message notifying them of the lost connection, regardless of whether that Intelligence Server was in a cluster.

MicroStrategy Web

If a cluster node shuts down while MicroStrategy Web users are connected, those jobs return an error message by default. The error message offers the option to resubmit the job, in which case MicroStrategy Web automatically reconnects the user to another node.

Customizations to MicroStrategy Web can alter this default behavior in several ways.

If a node is removed from the cluster, all existing connections continue to function and remain connected to that machine, although the machine no longer has access to the clustered nodes' resources. Future connections from MicroStrategy Web will be to valid cluster nodes.

Status After Reboot

If a node goes down for any reason, all jobs on that node are terminated. Restarting the node provides an empty list of jobs in the job queue.

If a node is forcefully shut down in a Windows environment, it automatically rejoins the cluster when it comes back up.

The nodes that are still in the cluster but not available are listed in the Cluster Monitor with a status of Stopped.