Examples of Cluster State Transitions

• If a remote cluster joins the global cluster configuration, the other clusters in the configuration transition their "view" of the remote cluster to the RUNNING state:

INIT -> BUILD -> RUNNING

• If a cluster loses all heartbeats to a remote cluster in the RUNNING state, inquiries are sent. If all inquiry responses indicate the remote cluster is actually down, the cluster transitions the remote cluster state to FAULTED:

RUNNING -> LOST_HB -> INQUIRY -> FAULTED

• If at least one response does not indicate the cluster is down, the cluster transitions the remote cluster state to UNKNOWN:

RUNNING -> LOST_HB -> INQUIRY -> UNKNOWN

• When the ClusterService service group, which maintains the connector process as highly available, fails over to another system in the cluster, the remote clusters transition their view of that cluster to TRANSITIONING, then back to RUNNING after the failover is successful:

RUNNING -> TRANSITIONING -> BUILD -> RUNNING

• When a remote cluster in a RUNNING state is stopped (by taking the ClusterService service group offline), the remote cluster transitions to EXITED:

RUNNING -> EXITING -> EXITED