Bug #27101 | mysqlhotcopy --record_log_pos retrieves wrong slave parameters | ||
---|---|---|---|
Submitted: | 13 Mar 2007 19:01 | Modified: | 22 Apr 2008 13:55 |
Reporter: | Alex Tomic | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 5.0.40-BK, 5.0.27 | OS: | Linux (Linux) |
Assigned to: | Iggy Galarza | CPU Architecture: | Any |
Tags: | Contribution, mysqlhotcopy, replication |
[13 Mar 2007 19:01]
Alex Tomic
[29 Mar 2007 6:39]
Valeriy Kravchuk
Thank you for a problem report and contributed patch. Verified with code review on latest 5.0.40-BK sources - mysqlhotcopy code is still the same. Your patch is surely worth developers' consideration.
[5 Mar 2008 19:13]
Andrei Elkin
Imo the problem was identified correctly. The fix is correct as well. Show slave status of mysql-4.0 output displays the necessary fields so that the patch should be applicable and workable with early version of the server.
[7 Mar 2008 20:46]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/43628 ChangeSet@1.2581, 2008-03-07 15:45:40-05:00, iggy@amd64.(none) +1 -0 Bug #27101 mysqlhotcopy --record_log_pos retrieves wrong slave parameters - Make sure mysqlhotcopy doesn't create unrestorable slaves.
[27 Mar 2008 22:04]
Bugs System
Pushed into 5.1.24-rc
[27 Mar 2008 22:11]
Bugs System
Pushed into 5.0.60
[28 Mar 2008 11:10]
Bugs System
Pushed into 6.0.5-alpha
[22 Apr 2008 13:55]
Paul DuBois
Noted in 5.0.60, 5.1.24, 6.0.5 changelogs. For the --record_log_pos option, mysqlhotcopy now determines the slave status information from the result of SHOW SLAVE STATUS by using the Relay_Master_Log_File and Exec_Master_Log_Pos values rather than the Master_Log_File and Read_Master_Log_Pos values. This provides a more accurate indication of slave execution relative to the master.