Binlog grows fast when a TencentDB for MySQL instance executes large transactions or lots of DML operations. MySQL’s data synchronization is based on binlog which ensures database restorability, stability, and high availability,
Before this upgrade, binlog files were stored in a special space provided by Tencent Cloud. As the speed of writing to binlog affects database performance, TencentDB for MySQL migrates the binlog files to high-performance SSDs (i.e., instance disk space), in order to improve database performance and stability.
This upgrade is applicable to two-node and three-node TencentDB for MySQL instances.
When a binlog file is generated, it is backed up via the automatic backup feature and its backup will be uploaded to COS.
After the upgrade starts, the space taken up by binlog files will be counted into the total used disk space, which may trigger alarms. We recommend the available disk space be larger than 20%.
You can shorten the local binlog retention period in the console. For more information, please see Configuring Local Binlog Retention Policy.
No. Before the upgrade, the instance expansion/reduction is based on the space taken up by data files.
After the upgrade, the instance expansion/reduction is based on the total used disk space and will notify you via SMS, Message Center, etc.
Currently, only the disk space utilization alarm is affected. Before the upgrade, the disk space utilization is calculated by "data file size/total disk space"; after the upgrade, it is calculated by "total used disk space/total disk space".