| Bug #112368 | Mismatched SQL for the same GTID transaction across primary and secondary | ||
|---|---|---|---|
| Submitted: | 17 Sep 2023 14:39 | Modified: | 21 Sep 2023 1:44 |
| Reporter: | huang rong | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Group Replication | Severity: | S1 (Critical) |
| Version: | 5.7.36 | OS: | Debian (Debian GNU/Linux 10 (buster)) |
| Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
| Tags: | GTID mismatch sql, InnoDB Cluster | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[17 Sep 2023 14:59]
huang rong
[17 Sep 2023 14:59]
huang rong
error.log of db8
Attachment: error.log.db8 (application/octet-stream, text), 59.01 KiB.
[17 Sep 2023 15:00]
huang rong
error.log of db7
Attachment: error.log.db7.sql (application/octet-stream, text), 55.75 KiB.
