ApsaraDB for Redis allows you to restart or rebuild a proxy node. This way, you can perform real-time disaster recovery drills. You can also perform O&M tasks when the service is unavailable or experiences a high latency.
- A cluster instance or a read/write splitting instance is used. For more information, see Cluster master-replica instances or Read/write splitting instances.
- The instance is an ApsaraDB for Redis Community Edition instance or a performance-enhanced or hybrid-storage instance of ApsaraDB for Redis Enhanced Edition (Tair). For more information, see Performance-enhanced instances and Hybrid-storage instances (phased out).
Proxy restart and rebuild may result in transient connections, which affect existing connections. Make sure that your applications can automatically reconnect to the proxy node. We recommend that you restart or rebuild a proxy node during off-peak hours.
- Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance is deployed. Then, find the instance and click its ID.
- In the left-side navigation pane, click Service Availability.
- In the Proxy Servers section, select the proxy node that you want to manage and click Restart.
- In the panel that appears, select Restart Mode.
- In-place Restart: restarts the proxy node.
- Rebuild Proxy: rebuilds the proxy node. If an issue cannot be fixed after the restart, select this mode.
- Click OK.