Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
6.4.0
-
None
-
Physical on prem and virtualised, MariaDB 3 node clusters
Description
Hi
We have 2 mariadb 3 node clusters behind maxscale. We are seeing an issue where binary logs aren't removed by PURGE BINARY LOGS TO. This manifests as the PURGE command returning without error but the log is not removed, and expire_logs_days is being ignored (or maybe is being actioned but the logs are removed). Example:
MariaDB [(none)]> show master logs;
|
+------------------+------------+
|
| Log_name | File_size |
|
+------------------+------------+
|
| mysql-bin.003024 | 1073742172 |
|
| mysql-bin.003025 | 1073763450 |
|
| mysql-bin.003026 | 1073752714 |
|
<snip>
|
+------------------+------------+
|
61 rows in set (0.000 sec)
|
|
MariaDB [(none)]> purge master logs to 'mysql-bin.003025';
|
Query OK, 0 rows affected (0.003 sec)
|
|
MariaDB [(none)]> show master logs;
|
+------------------+------------+
|
| Log_name | File_size |
|
+------------------+------------+
|
| mysql-bin.003024 | 1073742172 |
|
| mysql-bin.003025 | 1073763450 |
|
| mysql-bin.003026 | 1073752714 |
|
<snip>
|
+------------------+------------+
|
61 rows in set (0.000 sec)
|
|
MariaDB [(none)]>
|
We haven't made any manual changes to the binlog index file or anything like that. Also, so far we've only noted this behaviour on the node designated as the master by maxscale. No errors are recorded in the database log.
Thanks
Justin.