If an exception is detected on a master node of an ApsaraDB for Redis instance, the high availability (HA) module triggers a failover. The replica node corresponding to the master node takes over services, and the original master node becomes a replica node. Then, the HA module reconstructs the new replica node. If an exception is detected on a replica node of an ApsaraDB for Redis instance, the HA module reconstructs the replica node.
Content of the SMS message or email
A failover is triggered for your ApsaraDB for Redis instance r-bp1xxxxxxxxxxxxx (name: xxxxxx). Check whether your applications still connect to the ApsaraDB for Redis instance. We recommend that you enable automatic reconnection in your applications so that they can reconnect to the ApsaraDB for Redis instance after a failover.
Failover modes and impacts
| Trigger | Failover mode | Impact on business |
|---|---|---|
| A master node fails. | A failover is triggered to switch services to the corresponding replica node. The original master node becomes a replica node and is reconstructed. | During the failover, the ApsaraDB for Redis instance may be disconnected within seconds.
Reconstructing the replica node does not affect your business.
Note Make sure that your applications support automatic reconnection so that they can reconnect
to the ApsaraDB for Redis instance after a failover.
|
| A replica node fails. | No failover is triggered. The replica node is reconstructed. | None. |