Help Center/ Distributed Cache Service/ User Guide/ Changing an Instance/ Changing Cluster DCS Instances to be Across AZs
Updated on 2024-12-12 GMT+08:00

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

  1. Log in to the management console, and choose Application > Distributed Cache Service in the service list.
  2. Click in the upper left corner of the management console and select the region where your instance is located.
  3. In the navigation pane, choose Cache Manager.
  4. On the Cache Manager page, click a DCS instance.
  5. In the Network area of the DCS instance, click Enable Multi-AZ next to AZ.

    Figure 1 Enabling multi-AZ

  6. In the displayed Change AZs dialog box, specify Standby AZ.

    Figure 2 Selecting a standby AZ

  7. Set Apply Change to Now or During maintenance.
  8. Click OK.

    When complete, the task changes to the Successful state.