Setting a Local Retention Period for MySQL Binlogs

Scenarios

RDS for MySQL deletes local binlogs after they are backed up to OBS. You can set the local retention period for binlogs as required to fully utilize the instance space.

Binlogs can be retained from 0 to 168 (7x24) hours locally.

The rules for deleting local binlogs are as follows:

1. The binlogs used for replication between primary DB instances and standby DB instances or read replicas are not deleted, even when the retention period is set to 0.
2. To reduce the risk of full disk space, you can submit a service ticket to enable the forceful binlog deletion function. If the local space usage exceeds 80%, local binlogs (excluding those used for primary/standby replication) will be deleted forcibly regardless of the retention period configured for local binlogs. If the local space usage exceeds 90%, local binlogs (including those used for primary/standby replication) will be deleted forcibly regardless of the local retention period. By default, the data is not forcibly cleared. You can submit a service ticket to enable this function.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
4. On the Instance Management page, click the target DB instance.
5. In the navigation pane on the left, choose Backups & Restorations. On the Binlog Backups page, click Set Binlog Retention Period.
6. In the displayed dialog box, set the local retention period and click OK.
   Figure 1 Setting the binlog retention period