MySQL binlog cleanup

Linux Disk space is full solution

Query the overall disk usage command

df -h

*  / df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        3.8G     0  3.8G   0% /dev
tmpfs           3.8G     0  3.8G   0% /dev/shm
tmpfs           3.8G  393M  3.5G  11% /run
tmpfs           3.8G     0  3.8G   0% /sys/fs/cgroup
/dev/vda1        40G   30G  7.2G  81% /
tmpfs           777M     0  777M   0% /run/user/1000

Query the size of each folder or file in a directory

sudo du -sh *

*  / sudo du -sh * 
0	bin
211M	boot
...
2.2G	usr
26G	var

Then enter /var Under the table of contents , Continue to use this command to view , Found to be binlog Too much leads to , You need to remove binlog journal .

clear mysql binlog

mysql Of binlog essential , But if you don't clean it up , Xiaoyun disk can't stand frequent insertion and deletion every day . therefore binlog The log needs to be deleted .

mysql> show variables like ‘%expire%’;

After querying the above parameters, it is found that MySQL 8.0.12 On by default in the version binlog Log and set to binlog_format=row,binlog The expiration date parameter is binlog_expire_logs_seconds, Default 30 Days overdue .

notes ：
stay MySQL8.0 New parameter in version binlog_expire_logs_seconds, It can be accurate to seconds , In previous versions expire_logs_days In days , The minimum value is 1, stay MySQL8.0 GA This parameter is marked as deprecated .
stay MySQL 8.0 GA Version default use binlog_expire_logs_seconds, Time is 2592000 second ,30 God .

• If in MySQL Startup time inlog_expire_logs_seconds and expire_logs_days There is no set value , The default value is used binlog_expire_logs_seconds value , namely 30 God ;
• If in MySQL Startup time binlog_expire_logs_seconds perhaps expire_logs_days One of them is set to non 0 Value is not 0 Value as binlog Log expiration date ;
• If at startup binlog_expire_logs_seconds and expire_logs_days All parameters are set to non 0 Value is used binlog_expire_logs_seconds value ,expire_logs_days Value is invalid and an alarm message is sent .

To turn off auto clear binlog The function of the file needs to display the specified binlog_expire_logs_seconds=0 And don't set expire_logs_days Value .
In order to be compatible with previous versions, if the display specifies expire_logs_days =0 There is no designation binlog_expire_logs_seconds Value , Automatic cleaning at this time binlog The log is Ban Of , And at this point binlog_expire_logs_seconds The default value of does not apply .

Delete log manually

Manual cleaning certainly does not mean rm -rf ** , This may lead to binlog.index Disorder .

mysql -uroot -p #  land mysql
show binary logs; #  view log file 
show master status; #  View the log file being used ：binlog.000015
purge binary logs to 'binlog.000015'; #  Delete binlog.000015 Log files other than files 

Set expiration time

Set expiration 48 Hours

mysql> set global binlog_expire_logs_seconds=60*60*48;
mysql> flush logs; #  Brush it. log Make the above settings work , Otherwise it doesn't work . Be careful : Restart this configuration mysql Post failure .