Sample Header Ad - 728x90

MariaDB 11.7.2 do not rotate/purge binlog chunks (SOLVED)

1 vote
2 answers
135 views
MariaDB 11.7.2 is configured to keep binlog for 10800 seconds. RESET MASTER; performed. No slaves attached. Not a part of Galera. And no binlog rotation occured. Binlog chunks created but not purged. On attempt to purge an old chunks manually I got the next: MariaDB [(none)]> purge master logs to 'log-bin.000003'; Query OK, 0 rows affected, 1 warning (0.002 sec) MariaDB [(none)]> show warnings; +-------+------+-----------------------------------------------------------------------------------+ | Level | Code | Message +-------+------+-----------------------------------------------------------------------------------+ | Note | 1375 | Binary log 'log-bin.000001' is not purged because it is the current active binlog | +-------+------+-----------------------------------------------------------------------------------+ 1 row in set (0.000 sec) With current rate of operation disk will be overflown in a 48 hours. Periodic RESET MASTER; purges binlog completely but replication isn't possible under that circumstances. I have a little experience with MariaDB 11.x, maybe I have missed something important in my.cnf inherited from 10.x version. Something similar was found as a fixed bug: https://lists.mariadb.org/hyperkitty/list/commits@lists.mariadb.org/thread/2FXXPRGD7FMXEPPMVE763O7N6HDUANAB/ Any hints, suggestions, advices or even hypothesis are welcome. ---------- ---------- ---------- UPDATE From MariaDB 11.4 a new variable has been introduced: slave_connections_needed_for_purge If set to ON (default) binlog rotation will be disabled until SLAVE_IO connection will be established. binlog_expire_logs_seconds is completely ignored.
Asked by Kondybas (4800 rep)
May 16, 2025, 03:57 PM
Last activity: May 28, 2025, 05:46 PM