Shulou(Shulou.com)05/31 Report--

This article mainly introduces what are the common parameters of Galera cluster cluster in MySQL. It is very detailed and has certain reference value. If you are interested, you must finish it.

1 、 wsrep_local_state_uuid:

Consistent with the wsrep_cluster_state_uuid of the cluster

Root@ [(none)] > show status like'% wsrep_%_state_uuid%'

+-+

| | Variable_name | Value |

+-+

| | wsrep_local_state_uuid | eebe303f-5262-11e8-9e80-8a8d79151541 |

| | wsrep_cluster_state_uuid | eebe303f-5262-11e8-9e80-8a8d79151541 |

+-+

2 、 wsrep_last_committed:

The number of transactions committed by the cluster is a cumulative value, and all nodes should be equal. If there is inconsistency, there is a delay in the transaction, which can be used to calculate the delay.

Root@ [(none)] > show status like'% wsrep_last_committed%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_last_committed | 115562 | |

+-+ +

3 、 wsrep_replicated:

The number of write set copied from the local node. Wsrep_replicated_bytes is the total number of bytes of the write set. It can be used to refer to whether the load balance between nodes is balanced. The node with a higher value is busier.

Root@ [(none)] > show status like'% wsrep_replicated%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_replicated | 13579 | |

| | wsrep_replicated_bytes | 35585864 | |

+-+ +

4 、 wsrep_received:

Corresponding to wsrep_replicated, indicates the number of write set received from other nodes.

Root@ [(none)] > show status like'% wsrep_received%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_received | 11036 | |

| | wsrep_received_bytes | 35576367 | |

+-+ +

5 、 wsrep_local_commits:

The number of write set committed from the local node does not exceed the number of wsrep_replicated.

Root@ [(none)] > show status like'% wsrep_local_commits%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_local_commits | 13582 | |

+-+ +

6 、 wsrep_local_cert_failures:

During the synchronization process, the node authentication failure count, the conflict comes from the locally committed transaction and there is a lock conflict between the transaction in the synchronization queue, then the local verification fails (to ensure global data consistency).

Root@ [(none)] > show status like'% wsrep_local_cert_failures%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_local_cert_failures | 0 | |

+-+ +

7 、 wsrep_local_bf_aborts:

The number of write sets forcibly abandoned, and when there is a lock conflict between the local transaction and the transaction being executed in the synchronization queue, the first committed transaction is guaranteed to succeed, and the latter rollback or report an error.

Root@ [(none)] > show status like'% wsrep_local_bf_aborts%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_local_bf_aborts | 1 | |

+-+ +

8 、 wsrep_local_send_queue:

The length of the send queue. Wsrep_local_send_queue_avg: the average length from the last query status to the current send queue, > 0.0 means that the replication process has been throttled.

Root@ [(none)] > show status like'% wsrep_local_send_queue%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_local_send_queue | 0 | |

| | wsrep_local_send_queue_max | 2 | |

| | wsrep_local_send_queue_min | 0 | |

| | wsrep_local_send_queue_avg | 0.000145 | |

+-+ +

9 、 wsrep_local_recv_queue:

The length of the receive queue, corresponding to wsrep_local_send_queue.

Root@ [(none)] > show status like'% wsrep_local_send_queue%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_local_send_queue | 0 | |

| | wsrep_local_send_queue_max | 2 | |

| | wsrep_local_send_queue_min | 0 | |

| | wsrep_local_send_queue_avg | 0.000145 | |

+-+ +

10 、 wsrep_cert_deps_distance:

The average difference between the maximum seqno and the minimum seqno of a write set (write set) that can be executed in parallel.

Root@ [(none)] > show status like'% wsrep_cert_deps_distance%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_cert_deps_distance | 33.977434 | |

+-+ +

11 、 wsrep_apply_oooe:

The proportion of concurrent execution of transactions in the queue, the higher the value, the higher the efficiency.

Root@ [(none)] > show status like'% wsrep_apply_oooe%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_apply_oooe | 0.006204 | |

+-+ +

12 、 wsrep_commit_window:

Average concurrent commit window size.

Root@ [(none)] > show status like'% wsrep_commit_window%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_commit_window | 1.000423 | |

+-+ +

13 、 wsrep_local_state:

Status of the node, with a value of 1-6.

Value 1:The node starts and establishes a connection to the Primary Component.

Value 2:When the node succeeds with a state transfer request, it begins to cache write-sets.

Value 3:The node receives a State Snapshot Transfer. It now has all cluster data and begins to apply the cached write-sets.

Here the node enables Flow Control to ensure an eventual decrease in the slave queue.

Value 4:The node finishes catching up with the cluster. Its slave queue is now empty and it enables Flow Control to keep it empty.

The node sets the MySQL status variable wsrep_ready to the value 1. The node is now allowed to process transactions.

Value 5:The node receives a state transfer request. Flow Control relaxes to DONOR. The node caches all write-sets it cannot apply.

Value 6:The node completes the state transfer to joiner node.

Root@ [(none)] > show status like'% wsrep_local_state%'

+-+

| | Variable_name | Value |

+-+

| | wsrep_local_state_uuid | eebe303f-5262-11e8-9e80-8a8d79151541 |

| | wsrep_local_state | 4 |

| | wsrep_local_state_comment | Synced |

+-+

14 、 wsrep_incoming_addresses:

The addresses of other nodes in the cluster, separated by commas.

Root@ [(none)] > show status like'% wsrep_incoming_addresses%'

+-+

| | Variable_name | Value |

+-+

| | wsrep_incoming_addresses | IP1:3306,IP2:3306,IP3:3306 |

+-+

15 、 wsrep_cluster_conf_id:

The number of times the cluster node relationship has changed (+ 1 for each addition / deletion).

Root@ [(none)] > show status like'% wsrep_cluster_conf_id%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_cluster_conf_id | 53 | |

+-+ +

16. Wsrep_cluster_size: number of cluster nodes.

Root@ [(none)] > show status like'% wsrep_cluster_size%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_cluster_size | 3 | |

+-+ +

17 、 wsrep_cluster_status:

Current status of the cluster. Value: PRIMARY (normal) / NON_PRIMARY (inconsistent).

Root@ [(none)] > show status like'% wsrep_cluster_status'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_cluster_status | Primary |

+-+ +

18 、 wsrep_connected:

Whether the node is connected to the cluster. Value: ON/OFF.

Root@ [(none)] > show status like 'wsrep_connected'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_connected | ON |

+-+ +

19 、 wsrep_local_index:

Node id, with a value starting from 0. This node index in the cluster (base 0).

Root@ [(none)] > show status like 'wsrep_local_index'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_local_index | 0 | |

+-+ +

20 、 wsrep_ready:

Whether the node receives the query, that is, whether the node can be used normally.

Root@ [(none)] > show status like'% wsrep_ready%'

+-+ +

| | Variable_name | Value |

+-+ +

| | wsrep_ready | ON |

+-+ +

These are all the contents of the article "what are the common parameters of Galera cluster cluster in MySQL". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.