This section describes how to switch between primary/standby instances of the RDS for MySQL.
Application Scenarios
The eSurfing Cloud RDS for MySQL primary/standby instances support the high-availability function. In case of primary instance unavailability, an automatic master-slave switching is triggered. The access address of the instance remains unchanged after the switching. Additionally, manual triggering of the master-slave switching is supported for special service requirements.
Prerequisites
The instances must be primary/standby instances. The single instances and read-only instances do not support master-slave switching.
The instance status is Running.
Affect
During the primary/standby instance switching process, the instance service may be interrupted once or twice. Make sure that your application supports reconnection. Operate with caution.
If an instance is attached with read-only instances, it takes time to rebuild the replication link and synchronize incremental data after primary/standby instance switching, thus resulting in several minutes of delay in the data of the read-only instances.
Procedure
1. Log in to the Console.
2. Click 
in the upper left corner of the Console, and select Region and Project.
3. Select Database > Relational database... Go to the MySQL Console.
4. On the Instance Management page, select the specified instance, click More, and select Master-Slave Switching. A confirmation window will appear for you to recheck whether to perform the master-slave switching.
5. On the Task Center page, you can view the state of the master-slave switching task.