Configure scheduled events - Lindorm - Alibaba Cloud Documentation Center

In addition to notifications sent by voice call, email, or internal message, Operations and Maintenance (O&M) events for Lindorm, such as minor version upgrades, are also announced in the console. You can view scheduled events to see details such as the event type, region, procedure, notes, and the system's default switchover time. You can also manually modify the scheduled switchover time to manage the event execution order.

Notes

Notifications for system maintenance events for Lindorm, such as minor version upgrades, are typically sent 3 days before execution. For urgent threat fixes that require immediate attention, notifications are typically sent 3 days or less before execution. Notifications are sent by voice call, email, internal message, or through the console.

To ensure that you receive threat notifications promptly, log on to and complete the following steps:

Select ApsaraDB Fault or O&M Notification and Emergency Threat Alert Notification under Message Receiving Management > Basic Receiving Management > Exception Notification.
Set the message recipients to your database O&M personnel.

Procedure

Log on to the Lindorm console.
In the navigation pane on the left, choose Event Center > Scheduled Events.
On the Scheduled Events page, you can view the details of the events.
These details include the target instance ID, Region, and event type. For more information about the causes of events and their business impacts, see Event causes and impacts.
You can perform the following operations on an event:
- Change the scheduled switchover time.
  You can use the default switchover time or change the scheduled switchover time. The priority of the scheduled switchover time is higher than the priority of the default switchover time.
  1. On the Scheduled Event page, select one or more events.
  2. In the upper-left corner of the event list on the Scheduled Event page, click Config Scheduled Event.
  3. 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 specified by Scheduled Switching Time cannot be later than the time specified by Latest Execution Time.
  4. 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 update event. You can select a minor version update event and click Cancel Scheduled Event.

Event causes and impacts

Event cause	Impact type	Impact description
Minor version upgrade	Instance transient disconnection	After the scheduled switchover time, the following impacts occur. Perform this operation during off-peak hours and ensure your application has a reconnection mechanism. Single-zone instance: A switchover occurs. The instance or the shards involved in the switchover will experience a transient disconnection and will be in a read-only state for up to 30 seconds. This allows data to fully synchronize. Multi-zone instance: Two switchovers occur. During each switchover, the instance or the shards involved will experience a transient disconnection and will be in a read-only state for up to 30 seconds. This allows data to fully synchronize. The second switchover moves the primary node to the primary zone. This prevents issues such as increased access latency that can occur if the primary node remains in the secondary zone.
Minor version upgrade	Version number change	The content of updates varies by version. For more information, see the Version Guide.
Instance node O&M	Instance node O&M	After the scheduled switchover time, the node restarts for O&M. The restart and O&M process takes several minutes. During this process, the Region shards on the node are migrated. During the migration, latency for accessing the Region increases. The client application automatically retries to route requests to the new destination node. The instance remains readable and writable during the restart and O&M process. Perform this operation during off-peak hours.