Closed
Bug 1030671
Opened 10 years ago
Closed 10 years ago
Question about relay_log_purge
Categories
(Data & BI Services Team :: DB: MySQL, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gene, Unassigned)
Details
Currently Persona's Percona MySQL 5.1.68 DBs are configured with
relay_log_purge = 0
We recently filled the 50GB disk on one of our read slaves. I set this value to 1, restarted mysql and 36GB of bin logs were removed.
I've got this PR to make this change in our MySQL configs
https://github.com/mozilla/identity-ops/pull/161
I wanted to find out
* is this is a good setting to change?
* can I set this to "1" on slaves and masters?
* was it just a mistake that this was set to 0 when we started (Percona default?)?
Comment 1•10 years ago
|
||
Yes, the default is 1 and I don't know why you were set to 0.
The best solution for managing log files is to set relay_log_purge = ON (or 1, which is the default) and set expire_logs_days something manageable, such as 3-7 (what we use for most of our servers).
With this configuration, you shouldn't have logs older than 3-7 days.
Reporter | ||
Comment 2•10 years ago
|
||
Thanks!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Data & BI Services Team
You need to log in
before you can comment on or make changes to this bug.
Description
•