Bug #70 On 4.0.10, RESET SLAVE fails to reset the master's binlog coordinates
Submitted: 13 Feb 2003 8:25 Modified: 3 Mar 2003 6:49
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[13 Feb 2003 8:25] Guilhem Bichot 
Description:
On 4.0.10, RESET SLAVE fails to reset the master's binlog coordinates

How to repeat:
set up replication, do a few updates on the master, then do
STOP SLAVE
SHOW SLAVE STATUS
RESET SLAVE
SHOW SLAVE STATUS
and see how  Master_Log_File and Read_Master_Log_Pos
remain unchanged. They should be reset.

Suggested fix:
Workaround : after RESET SLAVE, stop the slave server (!) and restart it.

I'm debugging.
[13 Feb 2003 13:41] Guilhem Bichot 
Precisely, after RESET SLAVE, the coordinates displayed by SHOW SLAVE STATUS are un-reset, but they get reset at next START SLAVE. So the bug is just a bad display. And the workaround is to ignore the output from SHOW SLAVE STATUS.

I have a patch for 4.0, will send it together with #52 and #53.
[3 Mar 2003 6:49] Guilhem Bichot 
Thank you for your bug report. This issue has been fixed in the latest
development tree for that product. You can find more information about
accessing our development trees at 
    http://www.mysql.com/doc/en/Installing_source_tree.html