Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
11.4.2
-
None
-
Debian GNU/Linux 12 (bookworm)
Description
After upgrading to 11.4 we noticed that binlogs don't expire any more. I tried with a fresh setup on a test system, same result.
The server was configured with the following settings:
# mariadbd --print-defaults
|
mariadbd would have been started with the following arguments:
|
--socket=/run/mysqld/mysqld.sock --pid-file=/run/mysqld/mysqld.pid --basedir=/usr --bind-address=127.0.0.1 --server-id=1 --log_bin=/var/log/mysql/mysql-bin.log --max_binlog_size=1M --binlog_expire_logs_seconds=60 --character-set-server=utf8mb4 --character-set-collations=utf8mb4=uca1400_ai_ci |
To create some content for the binary logs I used sysbench
mariadb -e "CREATE DATABASE test;" |
sysbench oltp_common --db-driver=mysql --table-size=100000 --mysql-user=root --mysql-db=test prepare |
sysbench oltp_read_write --db-driver=mysql --table-size=100000 --mysql-user=root --mysql-db=test --threads=1 --report-interval=1 run |
- The log shows nothing except the normal startup lines
- With version 11.3, binlog files are removed automatically after ~1 minute. With 11.4 they stay
- Manually purging binary logs via "PURGE BINARY LOGS TO 'mysql-bin.000010';" works as expected in 11.3 but has no effect in 11.4 (also no error message)
Any suggestions to work around this bug are also welcome as the logs are filling the disk on the affected systems.
Attachments
Issue Links
- duplicates
-
MDEV-34504 PURGE BINARY LOGS not working anymore
-
- Closed
-