MySQL Bugs: #74812: Slave state/info docs not considering rbr

Bug #74812	Slave state/info docs not considering rbr
Submitted:	12 Nov 2014 9:30	Modified:	20 Aug 2015 15:41
Reporter:	Daniël van Eeden (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.6	OS:	Any
Assigned to:	David Moss	CPU Architecture:	Any

Description:
Page: http://dev.mysql.com/doc/refman/5.6/en/slave-sql-thread-states.html

"The State column for the I/O thread may also show the text of a statement. This indicates that the thread has read an event from the relay log, extracted the statement from it, and is executing it."

1. SQL is shown in the Info column, not in the State column
2. This does not guarantee it is executing that statement (Bug #74808)

How to repeat:
Compare docs with RBR replication with query info events.

Suggested fix:
Update docs

Hello Daniël,

Thank you for the bug report.

Thanks,
Umesh

Hello Daniël,
thanks for your feedback.
This is now fixed in the 5.6 and 5.7 documentation.

The new text:
"The Info column for the I/O thread may also show the text of a statement. This indicates that the thread has read an event from the relay log, extracted the statement from it, and may be executing it."

> 1. SQL is shown in the Info column, not in the State column
This is indeed fixed.

> 2. This does not guarantee it is executing that statement (Bug #74808)
This is sort-of-fixed. Maybe it should explain that it is executing the row based events generated by the statement shown...(and maybe there are more situations to consider here?)

I think there is a third item here what's wrong:
3. It's not the I/O thread, it's the SQL thread (that's why it's on the 'Replication Slave SQL Thread States' page)

Thanks for your feedback.

Re: 2) - this is why I used "and may be executing it." If there are other situations you think should be covered could you explain what they might be please?

Re: 3) - this has now been fixed in 5.6 and 5.7 documentation.