Slave Secondary Database Management

Users can create secondary databases (Slave) for the master database (Master) of a MySQL instance. For regions with multiple availability zones, the creation of secondary databases across availability zones is supported, that is, the master database instance and the secondary database are deployed in different availability zones, realizing disaster recovery capabilities at the availability zone level. The secondary database does not support batch creation, and can only be created for the master database (Master) of a MySQL instance at a time.

Create secondary database

Select the MySQL instance and click the "Create Secondary Database" button in the operation items.

In the pop-up window, select the availability zone where the secondary database is located, the database model (supporting the creation of different models for the primary and secondary databases) and the memory size (default primary database memory size), choose whether to lock the primary database (Master), input the name and port (default 3306) of the secondary database (Slave).

After clicking "Confirm", you come to the payment page. After confirming the payment, the secondary database (Slave) is successfully purchased and the initialization and data synchronization are carried out.

Note: The initialization time depends on the data volume.

Manage secondary database

The console of the slave secondary database of a MySQL instance provides management operation functions such as login, startup, restart, shutdown, configuration upgrade and downgrade, modification of configuration files, promotion to be primary database, deletion, renewal and monitoring and alert; for basic operations such as startup, shutdown, restart, etc., please refer to the basic operations of MySQL instance.

Promotion to primary database

Select the slave secondary database instance that needs to be promoted to the primary database, and click the "Promote to Primary Database" button in the operation items, and confirm in the pop-up window.

Redo secondary database

If the secondary database cannot continue to synchronize with the primary database, manual redo of the secondary database can be attempted, and the redo of the secondary database will export data from the primary database for data recovery. Before initiating the redo, a pre-check of redo conditions will be carried out first. For instances without exceptions, you can directly click to confirm and start the redo. For instances where the size of the non-transaction engine is more than 1G(the synchronization lock table time of the primary database is affected), the instance has long transactions(long transactions will cause the redo to not get the lock and always in the redo), and the instance replication relationship is incorrect(The unreasonable replication relationship will be erased), you need to manually tick to force and start redo.