Bug #113489 | gtid_executed table lost the last binlog gtids | ||
---|---|---|---|
Submitted: | 22 Dec 2023 7:43 | Modified: | 4 Jan 2024 3:36 |
Reporter: | xuty Lucky | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.26 5.7.36 5.7.44 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[22 Dec 2023 7:43]
xuty Lucky
[25 Dec 2023 15:05]
MySQL Verification Team
Hi, While this is rather impossible scenario (you need to kill/crash in a very specific way twice) even then I cannot reproduce this with 5.7.44. Your test case is on 5.7.26 that is rather old.
[4 Jan 2024 3:36]
xuty Lucky
I already reproduce this with 5.7.44: 1、use kill -9 mysqlpid, as emulate mysql crash; 2、start mysql with gdb with a break on Gtid_state::save ,when mysql start break on Gtid_state::save function, use kill -9 mysqlpid, as emulate mysql crash again when it in savegtid process but not completed; 3、normal start mysql 4、mysql.gtid_executed table will lost last binlog gtids,it will cause mysql use repeat gtid in binlog and slave replication maybe sync error;