•Every node in the cluster is aware of another system joining or leaving the cluster.
•Every node in the cluster is aware of the resources that are running on all nodes in the cluster.
•All nodes in the cluster are grouped under a common cluster name, which is used when accessing and managing the cluster.
Table
Table
State | Definition |
|
|
Down | The node is not actively participating in cluster operations. |
Joining | The node is in the process of becoming an active participant in the |
| cluster operations. |
Paused | The node is actively participating in cluster operations but cannot take ownership of |
| resource groups and cannot bring resources online. |
Up | The node is actively participating in all cluster operations, including hosting |
| cluster groups. |
Unknown | The state cannot be determined. |
|
|
When the Cluster Service is installed for the first time on a node, the administrator must choose whether that node forms its own cluster or joins an existing cluster. When the Cluster Service is started on a node, that node searches for other active nodes on networks enabled for internal cluster communications.
Forming a New Cluster
If a node cannot join a cluster, the node attempts to form the cluster by gaining control of the quorum disk. If the node gains control of the quorum disk, the node forms the cluster and uses the recovery logs in the quorum disk to update its cluster database. The Cluster Service maintains a consistent, updated copy of the cluster database on all active nodes.
Joining an Existing Cluster
A node can join an existing cluster if it can communicate with another cluster node. If a cluster exists and the joining node finds an active node, it attempts to join that node's cluster. If it succeeds, the Cluster Service then validates the node's name and verifies version compatibility. If the validation process succeeds, the node joins the cluster. The node is updated with the latest copy of the cluster database.
Using MSCS
59