Bug #83526 Purge Binary Logs freezes database when there are a large number of logs
| Submitted: | 25 Oct 2016 12:53 | Modified: | 2 Nov 2016 8:04 |
|---|---|---|---|
| Reporter: | Tyfanie Wineriter | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.6.23 | OS: | Red Hat |
| Assigned to: | CPU Architecture: | Any |
[25 Oct 2016 12:53]
Tyfanie Wineriter
[26 Oct 2016 1:40]
zhai weixiang
duplicate of bug#71901 ?
[26 Oct 2016 14:50]
Tyfanie Wineriter
hi Zhai, It does look like it's a duplicate of that bug. Do you know if there is a workaround? I don't see one on that bug page.
[27 Oct 2016 7:15]
zhai weixiang
It's not a big problem for us, because we always purge binlog files one by one. And configuring a bigger binlog file size (it's 500MB on our production) also help reducing the probability of rotating while purging expire logs.
[2 Nov 2016 8:04]
MySQL Verification Team
Thank you for the report. As Zhai rightly pointed in his initial note, this is most likely duplicate of Bug #71901. Thanks, Umesh
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.060 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.