Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.6.15
-
None
-
Ubuntu 20.04
Description
I've had to enable the slow log on a production server with lots of traffic to identify some issues however it was growing really fast in size.
I decided to add logrotate to compress and rotate the slow log when it exceeded 1G but to my surprise even though it was rotated and the size appeared smaller, the disk space wasn't actually freed until maria db was restarted
It appears that maria db is holding a lock to the file indefinitely for writing without ever releasing the lock thus the operating system can never release the space that was freed from log rotation
There should either be a way to rotate it via settings or allow the operating system to free the space
Attachments
Activity
There's an updated version on https://github.com/MariaDB/server/blob/11.3/support-files/mariadb.logrotate.sh with slightly better sizing, but depends how noisy the file is.
it's not enough to simply move the file somewhere, you need to tell the server to reopen logs after you moved them. That's why our debian packages install a proper logrotate file into / etc/logrotate.d. You can use it as an example.
Or see https://github.com/MariaDB/server/blob/10.6/debian/mariadb-server-10.6.mysql-server.logrotate