Node status outputs, among other information, cluster status variables.
The output format is
variable_value. Most of them are described in Galera Documentation Status Variables. Additionally we display:
- cluster_name - name of the cluster
- node_state - current state of the node:
- indexes_count - number of indexes managed by the cluster
- indexes - list of index names managed by the cluster
- nodes_set - list of nodes in the cluster defined with cluster
- nodes_view - actual list of nodes in cluster which this node sees
+----------------------------+-------------------------------------------------------------------------------------+ | Counter | Value | +----------------------------+-------------------------------------------------------------------------------------+ | cluster_name | post | | cluster_post_state_uuid | fba97c45-36df-11e9-a84e-eb09d14b8ea7 | | cluster_post_conf_id | 1 | | cluster_post_status | primary | | cluster_post_size | 5 | | cluster_post_local_index | 0 | | cluster_post_node_state | synced | | cluster_post_indexes_count | 2 | | cluster_post_indexes | pq1,pq_posts | | cluster_post_nodes_set | 10.10.0.1:9312 | | cluster_post_nodes_view | 10.10.0.1:9312,10.10.0.1:9320:replication,10.10.1.1:9312,10.10.1.1:9320:replication |
A multi-master replication cluster requires its single node to be started as a reference point before all the other nodes join it and form a cluster. This is called cluster bootstrapping which introduces a
primary component before others see that as a reference point to sync up the data from. The restart of a single node or reconnecting from a node after a shutdown can be done as usual.
After the whole cluster shutdown the server that was stopped last should be started first with
--new-cluster command line option (or run 'manticore_new_cluster' to start it via systemd). To make sure that the server is able to start as a reference point the
grastate.dat file located at the cluster path should be updated with the value of
safe_to_bootstrap option. I.e., both conditions,
safe_to_bootstrap=1, must be satisfied. An attempt to start any other node without these options set will trigger an error. To override this protection and start cluster from another server forcibly
--new-cluster-force command line option may be used. You can alternatively run
manticore_new_cluster --force to use systemd for that.
In case of a hard crash or an unclean shutdown of all the servers in the cluster you need to identify the most advanced node that has the largest
seqno in the
grastate.dat file located at the cluster path and start that server with the command line key
There are cases of multiple possible scenarios where searchd service got stopped with no node in the cluster being able to serve requests. In these cases someone needs to recover the cluster or part of it. Due to multi-master nature of Galera library used for replication, a cluster is like one logical entity and takes care about each its node and node's data consistency and keeps a cluster's status as a whole. This allows safe writes on multiple nodes at the same time and maintains cluster integrity unlike a traditional asynchronous replication.
Here we take a cluster of nodes A, B and C as an example and consider scenarios where some or all nodes are out of service and what to do to bring them back.
Node A is stopped as usual. The other nodes receive "normal shutdown" message from node A. The cluster size is reduced and a quorum re-calculation is issued.
After node A got started as usual, it joins the cluster nodes. Node A will not serve any write transaction until the join is finished and it's fully synchronized with the cluster. If a writeset cache on a donor node B or C, which is set with a Galera cluster's option gcache.size, still has all transactions missed at node A, node A will receive a fast incremental state transfer (IST), that is, a transfer of only missed transactions. Otherwise, a snapshot state transfer (SST) will start, that is, a transfer of index files.
Nodes A and B are stopped as usual. That is the same situation as in previous case but the cluster's size is reduced to 1 and node C itself forms primary component that allows it to handle write transactions.
Nodes A and B may be started as usual and will join the cluster after the start. Node C becomes a "donor" and provides the transfer of the state to nodes A and B.
All nodes are stopped as usual and the cluster is off.
The problem now is how to initialize cluster and it is important that on a clean shutdown of searchd nodes write the number of the last executed transaction into the cluster directory grastate.dat file along with the
safe_to_bootstrap key. The node stopped last will have the
safe_to_bootstrap: 1 option and the most advanced
It is important that this node should start first to form a cluster. To bootstrap, a cluster server should be started on this node with the --new-cluster command line key. On Linux you can also run
manticore_new_cluster which will start Manticore in
--new-cluster mode via systemd.
If another node starts first and bootstraps the cluster, then the most advanced node joins that cluster, performs full SST and receives an index file where some transactions are missed in comparison with index files it got before. That is why it is important to start the node that shut down last or to look at the cluster directory grastate.dat file to find the node with the
safe_to_bootstrap: 1 option.
Node A disappears from the cluster due to crash or network failure.
Nodes B and C try to reconnect to missed node A and after failure remove node A from the cluster. The cluster quorum is valid as 2 out of 3 nodes are running and the cluster works as usual.
After node A restarts it will join the cluster automatically the same way as in Case 1.
Nodes A and B disappear. Node C is not able to form the quorum alone as 1 node is less than 1.5 (half of 3). So the cluster on node C is switched to non-primary state and node C rejects any write transactions with an error message.
Meanwhile, the single node C is waiting for other nodes to connect and try to connect them itself. If this happens, after the network is restored and nodes A and B are running again, the cluster will be formed again automatically. If nodes A and B are just cut from node C, but they can still reach each other, they keep working as usual because they still form the quorum.
However, if both nodes A and B crashed or restarted due to power outage, someone should turn on primary component on the C node with a following statement:
But someone must make sure that all the other nodes are really unreachable before doing that, otherwise split-brain happens and separate clusters get formed.
SET CLUSTER posts GLOBAL 'pc.bootstrap' = 1
All nodes crashed. In this case the grastate.dat file at cluster directory is not updated and does not contain a valid sequence number
If this happened, someone should find the most advanced node and start the server on it with the --new-cluster-force command line key. All other nodes will start as usual as in Case 3).
On Linux you can also run
manticore_new_cluster --force. It will start Manticore in
--new-cluster-force mode via systemd.
Split-brain causes a cluster to get into non-primary state. For example, the cluster consists of even number of nodes (four), two couple of nodes being located in separate datacenters, and network failure interrupts the connection these datacenters. Split-brain happens as each group of nodes has exactly half of quorum. Both groups stop to handle write transactions as Galera replication model cares about data consistency and the cluster can not accept write transactions without quorum. But nodes in both groups try to re-connect to the nodes nodes from the other group to restore the cluster.
If someone wants to restore the cluster without network got restored the same steps as in Case 5 can be done but only at one group of nodes
After that, the group with the node we run this statement at can successfully handle write transactions again.
SET CLUSTER posts GLOBAL 'pc.bootstrap' = 1
However, we want to notice that if the statement gets issued at both groups this will end up with two separate clusters made, so the following network restoration will not make the groups to rejoin.