| Bug #72131 | Slave running state: System lock | ||
|---|---|---|---|
| Submitted: | 26 Mar 2014 5:52 | Modified: | 24 Apr 2020 19:41 |
| Reporter: | Shlomi Noach (OCA) | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.6.16-log | OS: | Linux (CentOS 5.9) |
| Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
| Tags: | replication, slave lag, System lock | ||
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
[26 Mar 2014 5:53]
Shlomi Noach
[20 Oct 2015 2:21]
monty solomon
performance schema data for affected slave
Attachment: benge.txt (text/plain), 989.87 KiB.
[20 Oct 2015 2:31]
monty solomon
performance schema data for affected slaveperformance schema data for affected slave
Attachment: sparkling-bonus.txt (text/plain), 1.36 MiB.
[20 Oct 2015 2:33]
monty solomon
performance schema data for affected slave
Attachment: dark-haze.txt (text/plain), 1.33 MiB.
[20 Oct 2015 2:43]
monty solomon
performance schema data for affected slave
Attachment: old-atom.txt (text/plain), 1.32 MiB.
[2 Oct 2017 14:54]
Khurram Naseem
Lag on one Read Replica
Attachment: Screen Shot 2017-10-02 at 7.53.48 PM.png (image/png, text), 168.60 KiB.
[29 Mar 2018 1:17]
Shinya Sugiyama
View for confirm system lock
Attachment: sys.system_lock_check.sql (application/octet-stream, text), 868 bytes.
