Usage notes
In most cases, you must configure notifications to be sent at least three days before the execution of system maintenance events (such as minor version updates),Lindorm and three or fewer days before the execution of vulnerability fix events. You can receive notifications by voice messages, emails, internal messages, or in-console messages.
To ensure that you can receive notifications in a timely manner, log on to Message Center and complete the following operations:
Select ApsaraDB Fault or Maintenance Notifications and Emergency Risk Warnings in the Fault Message section.
Configure the notification recipients. We recommend that you specify database O&M personnel as the recipients.

Procedure
Log on to the Lindorm console.
In the left-side navigation pane, choose .
On the Scheduled Event page, view the details about the events.
The event details include the instance ID, region, event type, cause, impact on business, scheduled switchover time, and status. For more information about the causes and impacts of events, see Causes and impacts of events.
You can perform the following operations on an event.
Modify Scheduled Switching Time.
You can use the default switchover time or modify the scheduled switchover time. The priority of the scheduled switchover time is higher than the priority of the default switchover time.
On the Scheduled Event page, select one or more events.
In the upper-right corner of the Scheduled Event page, click Config Scheduled Event.
In the Add Scheduled Event panel, set the scheduled switchover time.
If you want to immediately perform a switchover, select Earliest Execution Time. After you confirm the settings, the system immediately prepares for the switchover. If the preparation is already complete, the system immediately performs the switchover.
Note
The time that is specified by the Scheduled Switching Time parameter cannot be later than the time that is specified by the Latest Execution Time parameter.
Check whether the events that you selected are the events for which you want to apply the scheduled switchover time.
If the events that you selected are the events for which you want to apply the scheduled switchover time, click OK.
Otherwise, select the events for which you want to apply the scheduled switchover time in the Scheduled Event list and reconfigure the scheduled switchover time.
Cancel the scheduled switchover for an event.
You can cancel the scheduled switchover only for a minor version upgrade event. You can select a minor version upgrade event and click Cancel Scheduled Event.
Causes and impacts of events
Cause | Impact | Description |
Minor version update | Transient connection | At the scheduled switchover time, your instances may experience the following impacts. We recommend that you perform the switchover during off-peak hours and make sure that your applications are configured with a reconnection mechanism. Single-zone instances: One switchover is performed. During the switchover, your instance or the data shards in your instance experience transient connections and stay in the read-only state for up to 30 seconds before all data synchronized. Multi-zone instance: Two switchovers are performed. During the switchovers, your instance or data shards in your instance that are involved in the switchovers experience transient connections and stay in the read-only state for up to 30 seconds until all the data is synchronized. The second switchover switches the master node to the primary zone. This prevents an increase in access latency that may occur when the master node is in the secondary zone.
|
Version number change | The updated content vary with the version. For more information, see Release notes. |
Instance node O&M | Instance node O&M | After the scheduled event starts, the nodes of the instance are restarted and O&M operations are performed on the nodes. The restart and O&M operations are complete within minutes. During this process, all region shards on the nodes are migrated. During the migration, the latency of accessing the region increases because the client actively retries to route to the new node. You can still read data from or write data to the instance during this process. However, we recommend that you perform these operations during off-peak hours. |