You can view the cluster status information by checking the node status. This can be done using the Node status command, which displays various information about the node, including the cluster status variables.
The output format for the cluster status variables is as follows: cluster_name_variable_name variable_value. Most of the variables are described in the Galera Documentation Status Variables. In addition to these variables, Manticore Search also displays:
cluster_name- the name of the cluster, as defined in the replication setupnode_state- the current state of the node:closed,destroyed,joining,donor,syncedindexes_count- the number of tables managed by the clusterindexes- a list of table names managed by the clusternodes_set- the list of nodes in the cluster defined using theCREATE,JOINorALTER UPDATEcommandsnodes_view- the actual list of nodes in the cluster that the current node can see.state_uuid- UUID state of the cluster. If it matches the value in local_state_uuid, the local and cluster nodes are in sync.conf_id- total number of cluster membership changes that have taken place.status- cluster component status. Possible values are primary (primary group configuration, quorum present), non_primary (non-primary group configuration, quorum lost), or disconnected (not connected to group, retrying).size- number of nodes currently in the cluster.local_index- the node's index in the cluster.last_error- the last recorded error message related to a cluster operation. The message provides a high-level summary of the problem. For more detailed context, you should consult thesearchd.logfile.
During a State Snapshot Transfer (SST), a node provisions another by transferring a full data copy. This happens when a new node joins the cluster JOIN CLUSTER or when new tables are added ALTER CLUSTER ADD. While an SST is active, the following additional status variables will be available on both the donor and joiner nodes, with their progress kept in sync.
cluster_name_sst_total- The overall progress of the entire SST operation, from 0 to 100. This is the primary counter to watch.cluster_name_sst_stage- The name of the current work phase. The process cycles through these stages for each table being transferred:await nodes syncblock checksum calculateanalyze remotesend filesactivate tables
cluster_name_sst_stage_total- The progress of the current stage, from 0 to 100.cluster_name_sst_tables- The total number of tables being transferred in the SST.cluster_name_sst_table- The name and index of the table currently being processed (e.g.,3 (products)).
For most use cases, cluster_name_sst_total is sufficient. However, the other counters can be useful for investigating stalls or performance issues during a specific SST stage or on a particular table.
- SQL
- JSON
- PHP
- Python
- Python-asyncio
- javascript
- Java
- C#
- Rust
SHOW STATUS+---------------------------------+-------------------------------------------------------------------------------------+
| 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 | donor |
| 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 |
| cluster_post_sst_total | 65 |
| cluster_post_sst_stage | send files |
| cluster_post_sst_stage_total | 78 |
| cluster_post_sst_tables | 5 |
| cluster_post_sst_table | 3 (products) |
+---------------------------------+-------------------------------------------------------------------------------------+