| Bug #107991 | Clone_persist_gtid causes memory leak | ||
|---|---|---|---|
| Submitted: | 27 Jul 2022 2:02 | Modified: | 23 Oct 2023 8:31 |
| Reporter: | Baolin Huang | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
| Version: | 8.0.25 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Clone_persist_gtid, Contribution, Leak, memory leak | ||
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
[27 Jul 2022 2:02]
Baolin Huang
