Show slave status \g parameter details

Source: Internet
Author: User
Tags ssl connection

1. Row ***************************

Slave_io_state:waiting for Master to send event waits for master to occur

master_host: the current master server host

Master_user:backup is used to connect to the primary server's current user

master_port:3306 the current primary server interface

Current value of the CONNECT_RETRY:60 option

The name of the primary server binary log file that is currently being read by the I/O thread in master_log_file:mysql-bin.000010 slave

Read_master_log_pos:188793146 in the current primary server binary log, where I/O threads in slave have been read

RELAY_LOG_FILE:MYSQL-RELAY-BIN.000002 the name of the trunk log file that the SQL thread is currently reading and executing

relay_log_pos:186655308 where the SQL thread has been read and executed in the current trunk log

relay_master_log_file:mysql-bin.000010 name of the primary server binary log file containing most recent events executed by SQL thread

Slave_io_running:yes I/O threads are started and successfully connected to the primary server

Slave_sql_running:yes whether the SQL thread is started

Current value of the REPLICATE_DO_DB:REPLICATE-DO-DB option

Replicate_ignore_db:mysql the current value of the REPLICATE-IGNORE-DB option

Current value of the replicate_do_table:replicate-do-table option

Current value of the replicate_ignore_table:replicate-ignore-table option

Current value of the replicate_wild_do_table:replicate-wild-do-table option

Current value of the replicate_wild_ignore_table:replicate-wild-ignore_table option

Last_errno:0 Last error code

Last_error: Last Error content

Skip_counter:0 recently used values for Sql_slave_skip_counter

exec_master_log_pos:188793146 the location (relay_master_log_file) of the last time executed by the SQL thread from the primary server's binary log. In the primary server's binary log (Relay_master_log_file,exec_master_log_pos) corresponds to in the trunk log (Relay_log_file,relay_log_pos)

relay_log_space:186655464 Total size of all original trunk logs combined

Until_condition:none If you do not specify a Until clause, there is no value. If the secondary server is reading, the value is master until the primary server's binary log is reached at the given location. If the secondary server is reading until it reaches the given location of the secondary log, the value is relay

Until_log_file: Used to indicate the log file name, the log file name and location value define the point at which the SQL thread aborts execution

The until_log_pos:0 is used to indicate the log location value, and the log file name and location value define the point at which the SQL thread aborts execution

Master_ssl_allowed:no If you allow SSL connections to the primary server, the value is yes. If you do not allow SSL connections to the primary server, the value is no. If an SSL connection is allowed, but the secondary server does not have SSL support enabled, the value is ignored.

Current value of the MASTER_SSL_CA_FILE:MASTER-CA option

Current value of the Master_ssl_ca_path:master-capath option

Current value of the Master_ssl_cert:master-cert option

Current value of the Master_ssl_cipher:master-cipher option

               master_ssl_key:               The current value of the Master-key option

seconds_behind_master:0 This field is an indication of how much "backward" the subordinate server is. When a dependent SQL thread is running (processing an update), this field begins with the time stamp of the most recent event executed by this thread on the primary server, and the number of seconds elapsed. This field is zero when this thread is caught by a subordinate server I/O thread and goes into an idle state, waiting for more events from the I/O thread. In summary, this field measures the time gap between the subordinate server SQL thread and the subordinate server I/O thread, in seconds. If the network connection between the primary and secondary servers is faster, the subordinate server I/O threads are very close to the primary server, so this field can indicate very closely how much of the subordinate server SQL line turndown the primary server. This indication is inaccurate if the network is slow, and the subordinate SQL threads often catch up to the read slower subordinate server I/O thread, so seconds_behind_master often displays a value of 0. This is true even if the I/O thread lags behind the primary server. In other words, this column is only useful for fast networks. Even if the primary and secondary servers do not have the same clock, the time difference calculation will also work (when the slave server I/O thread starts, the difference is calculated.) and assume that the time difference will remain the same from now on. If the dependent SQL thread does not run, or if the subordinate server I/O thread is not running or is not connected to the primary server, then Seconds_behind_master is null (meaning "unknown"). For example, if the secondary server I/O thread sleeps for master-connect-retry seconds before reconnecting, NULL is displayed because the secondary server does not know what the primary server is doing, and cannot safely say how much. There is a limit to this field. The time stamp is retained through replication, which means that if a primary server M1 itself is a subordinate server M0, any event from Binlog of M1 (produced by replicating events from M0 's Binlog) has the same time stamp as the original event. This allows MySQL to successfully replicate the timestamp. However, the disadvantage of seconds_behind_master is that if M1 also receives direct updates from the client, the values change randomly, because sometimes the most recent M1 time comes from M0, sometimes from direct updates, and the most recent time stamp.







Master_server_id:1 the Server-id value of the primary server

This article from the "Years in the passing, shining still in" blog, please be sure to keep this source

Show slave status \g parameter details

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.