You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a 100MB database, and my production server fell over in the middle of the night after /var/log/mysql filled up with mariadb-bin files. I don't need binary logs because I'm not doing replication, and I expect that's true of a majority of users.
Per this StackOverflow answer, it is possible to define a custom override in /etc/mysql/conf.d which could either disable binlogging, or set the log retention period to something less that the 10 days it currently stands at.
Ansible novice here, but happy to attempt a PR if this would be useful.
The text was updated successfully, but these errors were encountered:
After looking into it, I'd be okay with disabling it by default. Anyone setting up MySQL replication will need to do a lot more manual work anyway so they could just re-enable it.
If you want to attempt the PR, this would be a good introduction to Ansible. It would look something like:
Add a task in roles/mariadb/tasks/main.yml and use the template action to create a conf file in /etc/mysql/conf.d.
Create the template in roles/mariadb/templates that the above action uses.
Create a default variable in roles/mariadb/defaults/main.yml which would act as a toggle.
Maybe just skip the task in 1 entirely using a when condition with the variable from 3.
I have a 100MB database, and my production server fell over in the middle of the night after
/var/log/mysql
filled up withmariadb-bin
files. I don't need binary logs because I'm not doing replication, and I expect that's true of a majority of users.Per this StackOverflow answer, it is possible to define a custom override in
/etc/mysql/conf.d
which could either disable binlogging, or set the log retention period to something less that the 10 days it currently stands at.Ansible novice here, but happy to attempt a PR if this would be useful.
The text was updated successfully, but these errors were encountered: