| Bug #96374 | binlog rotation deadlock when innodb concurrency limit setted | ||
|---|---|---|---|
| Submitted: | 30 Jul 2019 6:53 | Modified: | 31 May 2021 16:29 |
| Reporter: | jia liu | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | 8.0.16 8.0.17 5.7.25 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | binlog rotaion, innodb-commit-concurrency, innodb-thread-concurrency | ||
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
[30 Jul 2019 6:54]
jia liu
[30 Jul 2019 6:54]
jia liu
show engine innodb status
Attachment: show engine innodb status.txt (text/plain), 70.15 KiB.
[30 Jul 2019 6:55]
jia liu
show processlist
Attachment: show porcesslist.txt (text/plain), 135.61 KiB.
[13 Aug 2019 11:45]
jia liu
this is my comment, it is too long to post
Attachment: analyze.txt (text/plain), 24.03 KiB.
