new tool for binary logs handling

Registered by Olivier Doucet on 2012-10-30

Managing binary logs can be quite a pain.
if expire_log_days is not enough for your usage (need to rotate faster than 1 day, or need more control), you have to do the following steps :

- log on every slave and check latest timestamp / last log file read
- list the binary log files on master
- determine earliest file needed
- purge all log files up to (but not including) the earliest file. Or use timestamp (PURGE BINARY LOGS BEFORE '2012-10-02 22:46:26';)

This process is also described in officiel documentation here :
http://dev.mysql.com/doc/refman/5.5/en/purge-binary-logs.html

This could be done automatically by a smart tool, that could find all slaves (or rely on user input), check everything needed, and issue PURGE LOGS instructions as necessary.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.