To clean MySQL binlog files, you should use the PURGE BINARY LOGS command or set the automatic expiration time, and files cannot be deleted directly. 1. Use the PURGE command to clean old logs by file name or time. Before execution, you need to confirm that the slave library no longer uses the relevant logs; 2. Check the current log status and slave library location through SHOW MASTER STATUS and SHOW SLAVE STATUS to ensure the security of the cleaning range; 3. MySQL 8.0 recommends setting the binlog_expire_logs_seconds parameter to achieve automatic cleaning, which is suitable for long-term operating environments; 4. Deleting files directly will cause serious problems such as master-slave synchronization failure and inconsistent log information, which must be avoided. Mastering these methods can efficiently free up disk space while ensuring data security.
MySQL's binlog file records all changes to the database and is very important for master-slave replication and data recovery. But over time, these files take up a lot of disk space. Many people directly delete files and release space, which resulted in MySQL errors and even service exceptions. In fact, there are standard methods to clean binlog, as long as you follow the steps, it is both safe and efficient.
Clean up using the PURGE BINARY LOGS command
This is the most recommended way. MySQL provides special commands to safely delete old binlog files without affecting the logs currently in use.
grammar:
-
Clean by file name:
PURGE BINARY LOGS TO 'mysql-bin.010';
This deletes all binlog files with a number less than
mysql-bin.010
. Clean up by time:
PURGE BINARY LOGS BEFORE '2024-01-01 00:00:00';
Delete logs before the specified time.
Note: Before execution, confirm that the slave library is still using the log you want to delete, otherwise it may cause the master-slave synchronization to be interrupted.
Check the current binlog status and location
Before starting, it is important to understand the current status of the binlog to avoid mistaken deletion.
You can run:
SHOW MASTER STATUS;
This displays the binlog file name currently being written.
If the master-slave architecture is used, it must be executed on each slave library:
SHOW SLAVE STATUS\G
Check Relay_Master_Log_File
and Exec_Master_Log_Pos
to make sure that the log range you reserve covers all reads from the library.
Setting the automatic expiration time (recommended by MySQL 8.0)
If you are using MySQL 8.0 and above, you can directly set the binlog automatic expiration time to save manual maintenance.
Setting method:
SET GLOBAL binlog_expire_logs_seconds = 604800; -- 7 days
It can also be written into the configuration file (my.cnf or my.ini):
[mysqld] binlog_expire_logs_seconds=604800
In this way, MySQL will automatically clean up binlogs that have exceeded the set time in the background, which is suitable for long-term and stable operation environments.
It is not recommended to delete files directly
For convenience, some users directly go to the file system to delete binlog files, such as:
rm -f /var/lib/mysql/mysql-bin.001
This is very dangerous. MySQL does not know which files you deleted may cause:
- Master-slave synchronization failed
- Missing critical logs during data recovery
- The information displayed by
SHOW BINARY LOGS
is inconsistent
If you have to delete it manually, you must stop MySQL first, or use the PURGE
command before processing.
Basically that's it. Be careful when cleaning binlogs, especially in production environments. Mastering the above methods can basically deal with most scenarios.
The above is the detailed content of How to safely purge old MySQL binlog files?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_

The key steps for installing MySQL on Windows 11 are as follows: 1. Download the correct version, select the Windows MSI installation package and ensure that the system is 64-bit; 2. Select the "Custom" mode during installation, add MySQLServer and set the appropriate installation path; 3. Run the configuration wizard, select the "ServerComputer" configuration type, set the root password, and select the automatic startup method; 4. After the test installation is successful, if the prompt command is unavailable, add the MySQL bin directory to the system PATH environment variable. Follow these steps to complete the installation and configuration smoothly.

To reset the root password of MySQL, please follow the following steps: 1. Stop the MySQL server, use sudosystemctlstopmysql or sudosystemctlstopmysqld; 2. Start MySQL in --skip-grant-tables mode, execute sudomysqld-skip-grant-tables&; 3. Log in to MySQL and execute the corresponding SQL command to modify the password according to the version, such as FLUSHPRIVILEGES;ALTERUSER'root'@'localhost'IDENTIFIEDBY'your_new

When handling NULL values ??in MySQL, please note: 1. When designing the table, the key fields are set to NOTNULL, and optional fields are allowed NULL; 2. ISNULL or ISNOTNULL must be used with = or !=; 3. IFNULL or COALESCE functions can be used to replace the display default values; 4. Be cautious when using NULL values ??directly when inserting or updating, and pay attention to the data source and ORM framework processing methods. NULL represents an unknown value and does not equal any value, including itself. Therefore, be careful when querying, counting, and connecting tables to avoid missing data or logical errors. Rational use of functions and constraints can effectively reduce interference caused by NULL.
