| Bug #90137 | executed_gtid_set is empty after mysql crash | ||
|---|---|---|---|
| Submitted: | 20 Mar 2018 10:40 | Modified: | 23 May 2018 1:24 |
| Reporter: | Prasad N | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
| Version: | 5.7.18 | OS: | CentOS (2.6.32-696.23.1.el6.x86_64 ) |
| Assigned to: | MySQL Verification Team | CPU Architecture: | x86 |
| Tags: | crash, execute_gtid_set, GTID | ||
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
[20 Mar 2018 10:49]
Prasad N
[23 May 2018 1:27]
Prasad N
mysqld logs having this issue
Attachment: mysqld.log (application/octet-stream, text), 9.50 KiB.
