Comments on: The “once and for all” SHOW SLAVE STATUS log files & positions explained https://shlomi-noach.github.io/blog/mysql/the-once-and-for-all-show-slave-status-log-files-positions-explained Blog by Shlomi Noach Thu, 07 Jul 2016 17:04:33 +0000 hourly 1 https://wordpress.org/?v=5.3.3 By: shlomi https://shlomi-noach.github.io/blog/mysql/the-once-and-for-all-show-slave-status-log-files-positions-explained/comment-page-1#comment-366453 Thu, 07 Jul 2016 17:04:33 +0000 https://shlomi-noach.github.io/blog/?p=6732#comment-366453 @Marc,

You are 100% correct. Thank you!

]]> By: Marc https://shlomi-noach.github.io/blog/mysql/the-once-and-for-all-show-slave-status-log-files-positions-explained/comment-page-1#comment-366302 Wed, 06 Jul 2016 14:14:29 +0000 https://shlomi-noach.github.io/blog/?p=6732#comment-366302 If the network is bad the slave might lag behind the master even though Exec_Master_Log_Pos == Read_Master_Log_Pos. If those two are equal it just means that the SQL Thread has executed everything the IO Thread has read, doesn’t it?

]]> By: Hetul https://shlomi-noach.github.io/blog/mysql/the-once-and-for-all-show-slave-status-log-files-positions-explained/comment-page-1#comment-342415 Wed, 13 Jan 2016 09:44:47 +0000 https://shlomi-noach.github.io/blog/?p=6732#comment-342415 While the slave fetches entries and writes them into the relay log (via the IO_THREAD), it also reads the relay log to replay those entries (via the SQL_THREAD).
What does this mean ?

]]> By: solomon https://shlomi-noach.github.io/blog/mysql/the-once-and-for-all-show-slave-status-log-files-positions-explained/comment-page-1#comment-314755 Fri, 17 Apr 2015 16:09:00 +0000 https://shlomi-noach.github.io/blog/?p=6732#comment-314755 Thanks for clever explanation

]]> By: leafonsword https://shlomi-noach.github.io/blog/mysql/the-once-and-for-all-show-slave-status-log-files-positions-explained/comment-page-1#comment-297978 Sun, 21 Dec 2014 08:16:52 +0000 https://shlomi-noach.github.io/blog/?p=6732#comment-297978 Good explaination graph!

]]> By: Amit https://shlomi-noach.github.io/blog/mysql/the-once-and-for-all-show-slave-status-log-files-positions-explained/comment-page-1#comment-248141 Tue, 01 Jul 2014 18:06:24 +0000 https://shlomi-noach.github.io/blog/?p=6732#comment-248141 very helpful. good explanation of 6 parameters and mainly of relay_master_log_file and exec_master_log_pos.
thanks.

]]> By: shlomi https://shlomi-noach.github.io/blog/mysql/the-once-and-for-all-show-slave-status-log-files-positions-explained/comment-page-1#comment-232550 Fri, 07 Mar 2014 14:16:24 +0000 https://shlomi-noach.github.io/blog/?p=6732#comment-232550 Both!
Here’s a sample:

140307  9:11:28 [Note] Slave SQL thread initialized, starting replication in log 'mysqld-bin.001197' at position 372630617, relay log '/path/to/mysqld-relay-bin.000835' position: 3591147
140307  9:11:28 [Note] Slave I/O thread: connected to master 'mysql_replication@mymaster-107:3306',replication started in log 'mysqld-bin.001197' at position 374979349

The first entry is the SQL thread, talking about the execution position and the matching relay log position.
The second is the I/O thread, which notes the position that is being fetched.

]]> By: Shantanu Oak https://shlomi-noach.github.io/blog/mysql/the-once-and-for-all-show-slave-status-log-files-positions-explained/comment-page-1#comment-232546 Fri, 07 Mar 2014 13:07:06 +0000 https://shlomi-noach.github.io/blog/?p=6732#comment-232546 The error log would mention the master log file and position when the slave stops. Is it “Master Log File” or “Relay Master log file” that is shown in the error log?

]]>