From time-to-time you may need to manually purge binary logs on your MySQL slaves to free up a bit of disk space. We can achieve this by using the PURGE BINARY LOGS command from the MySQL command line client. MySQL advises the following procedure when purging these logs
To safely purge binary log files, follow this procedure:
- On each slave server, use
SHOW SLAVE STATUSto check which log file it is reading.
- Obtain a listing of the binary log files on the master server with
SHOW BINARY LOGS.
- Determine the earliest log file among all the slaves. This is the target file. If all the slaves are up to date, this is the last log file on the list.
- Make a backup of all the log files you are about to delete. (This step is optional, but always advisable.)
- Purge all log files up to but not including the target file. source
The below example will purge all binary logs older than the one called backup-master.001271.
Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2640654 Server version: 5.1.34-log SUSE MySQL RPM Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> PURGE BINARY LOGS TO 'backup-master.001271'
Provided your slave is running this command is reasonably safe as MySQL will prevent you from purging any log files that are currently being read. If the slave thread is not running then you do have to make sure you are not purging a needed file. If you purge a needed file the slave will break when it is restarted. You can also use the expire_logs_days variable to automatically control when binary logs are purged.