| Bug #91690 | MySQL Slave server consume all memory and swap compare to other slave and master | ||
|---|---|---|---|
| Submitted: | 18 Jul 2018 3:18 | Modified: | 21 Jul 2018 1:52 |
| Reporter: | Joey Aldrin Cruz | Email Updates: | |
| Status: | Unsupported | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.6.11 | OS: | CentOS (6.9 Final) |
| Assigned to: | MySQL Verification Team | CPU Architecture: | x86 (any) |
| Tags: | Memory, MySQL, slave, swap | ||
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
[18 Jul 2018 3:30]
Joey Aldrin Cruz
[18 Jul 2018 3:30]
Joey Aldrin Cruz
global_status_result
Attachment: global status.txt (text/plain), 40.58 KiB.
[18 Jul 2018 3:30]
Joey Aldrin Cruz
global_variables_result
Attachment: global_variables.txt (text/plain), 52.23 KiB.
[19 Jul 2018 9:29]
Joey Aldrin Cruz
top_result_current
Attachment: top_current_swap.PNG (image/png, text), 15.43 KiB.
[19 Jul 2018 10:18]
Joey Aldrin Cruz
current processlist while on 120GB of swap and 97.7% of memory usage
Attachment: current_processlist.txt (text/plain), 1.54 KiB.
