Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
5.5(EOL), 10.0(EOL)
-
None
-
3 node Galera Cluster
Linux version 3.13.0-48-generic (buildd@orlo) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #80-Ubuntu SMP Thu Mar 12 11:16:15 U
TC 2015 (Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16)
-
10.1.15, 10.1.20, 10.1.22, 10.1.29
Description
There is an intermittent bug whereby the binary log does not rotate . The binary log size is set at 100MB yet there are times it does not rotate and exceeds 100MB .
The binary log has sometimes grown to 60GB in size . Commands like FLUSH LOGS do not achieve rotation . When a binary log file becomes more than 10 days old, it is supposed to be deleted by the database server , this is not happening once hit by the bug .
The Mariadb node has to be restarted to rotate the binary log once it grows above 100MB . Parameters like max-bin-log and expire-logs-days are configured correctly .
max_binlog_size | 104857600
expire_logs_days | 8
Attachments
Issue Links
- includes
-
MDEV-9510 Segmentation fault in binlog thread causes crash
-
- Closed
-
- relates to
-
MDEV-8746 max_binlog_size was exceeded
-
- Closed
-
-
MDEV-11610 Logrotate to only FLUSH LOCAL ERROR LOGS, ENGINE LOGS, GENERAL LOGS
-
- Closed
-
The very reported cluster-related issue has been fixed by
MDEV-9510. I am not sure whether followup comments mentioning 5.5 still present an outstanding issue. If they are valid could you please make us known via either writing to this ticket, or better to report a new one.Thanks.