http://galeracluster.com/documentation-webpages/monitoringthecluster.html#monitoring-cluster
At Node 1
MariaDB [(none)]> show status like 'wsrep_cluster_state_uuid';
Node 2 and Node 3 should return same UUID
To check cluster integrity, for each node complete the following steps:
- Check that the node is part of the cluster:
At Node 1
MariaDB [(none)]> show status like 'wsrep_cluster_state_uuid';
MariaDB [(none)]> show status like 'wsrep_cluster_state_uuid';
+--------------------------+--------------------------------------+
| Variable_name | Value |
+--------------------------+--------------------------------------+
| wsrep_cluster_state_uuid | e48cd2c2-ab6e-11e4-a8af-268a757dde7a |
+--------------------------+--------------------------------------+
1 row in set (0.00 sec)
Node 2 and Node 3 should return same UUID
- Check that the node belongs to the same component:Each node in the cluster should provide the same value. If you find a node that carries a different value, this indicates the cluster is partitioned. Once network connectivity is restored, the value will align itself with the others.
On the first node check cluster size:-
> show status like 'wsrep_cluster_size';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
| wsrep_cluster_size | 3 |
+--------------------+-------+
If the value equals the expected number of nodes in the cluster, all nodes are connected to the cluster.
Note
You only need to check the cluster size on one node.
Check primary cluster status
show status like 'wsrep_cluster_status';
+----------------------+---------+
| Variable_name | Value |
+----------------------+---------+
| wsrep_cluster_status | Primary |
The node should return a value of Primary. Other values indicate that the node is part of a nonoperational component. This can occur in cases of multiple membership changes and a loss of quorum or in the case of a split-brain condition.
- Check the node status:If the value is TRUE, the node can accept SQL load.
- If the wsrep_ready value is FALSE, check that the node is connected:If the value is OFF, the node has not connected to any of the cluster components. This may relate to misconfiguration. For instance, if the node uses invalid values forwsrep_cluster_address or wsrep_cluster_name.Check the error log for proper diagnostics.
- If the node is connected, but still cannot accept SQL load, check that the node is part of the Primary Component:If the the state comment is Joining, Waiting for SST, or Joined, the node is syncing with the cluster.
No comments:
Post a Comment