Bug #73720 | `SHOW SLAVE STATUS` != slave_relay_log_info when replicating DDL | ||
---|---|---|---|
Submitted: | 26 Aug 2014 2:31 | Modified: | 7 Nov 2014 1:51 |
Reporter: | Tac Huang | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 5.6.19, 5.6.21 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[26 Aug 2014 2:31]
Tac Huang
[26 Aug 2014 10:30]
MySQL Verification Team
Hello Tac Huang, Thank you for the bug report and test case. Observed that Master_log_pos and Exec_Master_Log_Pos were indeed different. Thanks, Umesh
[7 Nov 2014 1:51]
Tac Huang
Myisam DML encounter same problem in 5.6.20. It seems that "relay_log_info_repository = TABLE" is less crash-safe than "relay_log_info_repository = FILE" in Myisam DML.