Promoting a Read Replica to Primary
Scenarios
If your DB instance fails and you want to quickly obtain a readable and writable instance, promote one of the instance's read replicas to primary.
After a read replica is promoted to primary, the replication relationship between the read replica and its primary instance is removed and the read replica serves as a standalone DB instance. Promoting a read replica has no impact on its original primary DB instance.
Constraints
- This function is available only to RDS for MySQL 5.7 and 8.0.
- Only pay-per-use read replicas can be changed to standalone DB instances.
- This function is unavailable for DB instances with proxy enabled.
- Only general-purpose and Kunpeng general-enhanced read replicas using cloud SSDs can be promoted to primary.
Procedure
- Click
in the upper left corner and select a region.
- Click
in the upper left corner of the page and choose Databases > Relational Database Service.
- On the Instances page, locate the target RDS for MySQL instance and click
in front of it to expand the read replica list.
- Find the desired read replica and choose
in the Operation column.Figure 1 Locating a read replica
- In the displayed dialog box, click Yes.
Figure 2 Promoting a read replica to primary
- After the promotion is complete, check and manage the new instance on the Instances page.
- During the promotion, the read replica status is Promoting to primary. Upon the completion of the promotion, a full backup is automatically performed.
- After the read replica is promoted to primary, it is disassociated from the original DB instance. Its Status becomes Available and DB Instance Type becomes Single.
- The billing mode on the new instance remains unchanged.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot