Changing Cluster DCS Instances to be Across AZs
To implement disaster recovery, cluster instances (whose master and standby nodes are) in a single AZ can be deployed across AZs by migrating the standby nodes to other AZs.
Notes and Constraints
- Available only for single-AZ cluster instances with two or more replicas.
- When you enable multi-AZ for a Proxy Cluster instance:
- Service running may fluctuate during the change. Perform this operation during off-peak hours.
- If your application cannot reconnect or handle exceptions, try restarting the application after the change.
- When you enable multi-AZ for a Redis Cluster instance:
- Changing AZs will not interrupt services or the master node, but will slightly affect performance. Perform this operation during off-peak hours.
- Changing AZs interrupts connections to some replicas. Ensure your application can automatically recover from exceptions and reconnect to Redis.
Procedure
- Log in to the management console, and choose Application > Distributed Cache Service in the service list.
- Click
in the upper left corner of the console and select the region where your instance is located.
- In the navigation pane, choose Cache Manager.
- On the Cache Manager page, click a DCS instance.
- In the Network area of the DCS instance, click Enable Multi-AZ next to AZ.
Figure 1 Enabling multi-AZ
- In the displayed Change AZs dialog box, specify Standby AZ.
Figure 2 Selecting a standby AZ
- Set Apply Change to Now or During maintenance.
- Click OK.
When complete, the task changes to the Successful state.
Related Document
To learn about the cross-AZ DR architecture of a cluster DCS Redis instance, see Cross-AZ DR Within a Region.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.