I have a Master-Slave replication setup and it looks like that it is running fine. Below is a result of SHOW SLAVE STATUS command:

show slave STATUS\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: *.*.*.*
                  Master_User: repliV1
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000001
          Read_Master_Log_Pos: 10726644
               Relay_Log_File: mysqld-relay-bin.000056
                Relay_Log_Pos: 231871
        Relay_Master_Log_File: mysql-bin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: data1
                   Last_Errno: 0
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 10726644
              Relay_Log_Space: 232172
              Until_Condition: None
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
        Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
               Last_SQL_Errno: 0

I would like to understand further about the Relay_Log_File, Relay_Log_Pos and Relay_Master_Log_File.

My questions are:

  • Is it true that the relay log file is one which is being read and stored locally for the replication to run ?

  • What about the relay_master_log_file then; how is it different from the Master_Log_File?

  • What are both of these values, viz., Read_Master_Log_Pos and Relay_Log_Pos ? Why are they showing up even though the replication is complete and in sync ?

  • Is it true that these files are in binary format, and hence I cannot view them ?


I want to understand further is the Relay_Log_File, Relay_Log_Pos and Relay_Master_Log_File.

From SHOW SLAVE STATUS\G, get two values

  • Relay_Log_File : Current relay log accepting new entries during replication
  • Relay_Log_Pos : Current position of the current relay log accepting new entries during replication
  • Relay_Master_Log_File : Relay log file containing the last successfully executed SQL statement on the Master that was executed on the Slave.
  • Master_Log_File : The log on the Master that corresponds to the current relay log file and current relay log position

The files are in binary so not able to view them right

Yes, you can view the relay logs. Since they have the same structure as a regular binary log, just run the mysqlbinlog program. For example to view the SQL within any of you relay logs, such as the last one, do this:

mysqlbinlog mysqld-relay-bin.000056 > /root/SQLForCurrentRelayLog.txt
less /root/SQLForCurrentRelayLog.txt
| improve this answer | |
  • I am now clearer how about Exec_Master_Log_Pos (is this the executing master log position) and until_log_pos where to stop is it? – newbie14 May 26 '12 at 16:52
  • Minor mistake here. Relay_Master_Log_File is the name of the master binary log file containing the most recent event executed by the SQL thread, not the relay log file. – crishoj Sep 18 '16 at 13:03
  • @RolandoMySQLDBA ayudame porfavor dba.stackexchange.com/questions/177277/… – Ivan More Flores Jun 26 '17 at 15:36

Relay_Master_Log_File is actually the name of the binlog on the master containing the last SQL statement successfully executed on the slave. It is not the name of a relay log on the slave. See: http://dev.mysql.com/doc/refman/5.5/en/show-slave-status.html

Exec_Master_Log_Pos is the position in the relay_master_log_file that the slave SQL thread has executed up to. So in your example, the slave db has executed all statements up until binlog mysql-bin.000001 pos 10726644 on the master db.

until_log_pos is really only used if you start your slave with the syntax START SLAVE UNTIL master_log_pos = $integer. That syntax will replicate up to that position (it will be the exec_master_log_pos) and then stop. You would normally only do this if you wanted to replicate to a specific point, but no further (like if the next statement is an accidental table drop or something). The value of until_log_pos is 0 when it is not specified, so in your case means that replication will just keep moving forward.

| improve this answer | |
  • thank you I am getting even clearer now. Anything else to monitor now? – newbie14 May 30 '12 at 16:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.