View and manage scheduled events in ApsaraDB for MongoDB - ApsaraDB for MongoDB

You can receive notifications for scheduled events such as instance migrations and version upgrades by phone call, email, or internal message or in the ApsaraDB for MongoDB console. You can view information such as the event types, causes, and business impacts of scheduled events. You can also change the scheduled time of a business switchover that is triggered by the scheduled events.

Prerequisites

Scheduled O&M events exist in ApsaraDB for MongoDB.

Note

In the top navigation bar of the ApsaraDB for MongoDB console, click the Scheduled Events button to check the number of scheduled events.

Precautions

You are notified of ApsaraDB for Redis pending events such as instance migrations or version upgrades at least three days before the events occur. Notifications for high-risk vulnerability fixes are sent three or fewer days before execution due to the urgency of these events. Event notifications are sent by using phone calls, emails, internal messages, or the ApsaraDB for Redis console. To use this feature, log on to the Message Center console, enable ApsaraDB Fault or Maintenance Notifications, and then specify a contact. We recommend that you specify an O&M engineer as the contact.

Procedure

Log on to the ApsaraDB for MongoDB console.
In the left-side navigation pane, click Scheduled Events.
Important
If a pending event requires you to schedule the time to handle the event, a message that prompts you to schedule the time at the earliest opportunity appears.

On the Scheduled Event page, perform the following operations:

View the event details
The following columns are displayed on the Scheduled Event page: Event Type, Cause, Business Impact, Start At, Scheduled Disconnection Time, Set Before, Status, Database Type, and Cancelable. You can view the corresponding attributes of instances in the preceding columns. For more information about the causes and business impacts of the events, see Causes and impacts of events.

Configure the switchover time

Scheduled events support the following switchover time modes: scheduled switchover time, periodic switchover time, and instance maintenance window, which are listed in the descending order of priority.

Switchover time mode	Operation
Scheduled switchover time	On the Scheduled Event page, select one or more events. In the upper-left corner of the Scheduled Event page, click Add Scheduled Event. In the Schedule Event panel, set the scheduled switching time. Note If you select Earliest Execution Time, the system automatically enters the earliest execution date and time. After you save the settings, the instances prepare for the switchover and enter the Pending state. If you do not select this option, you can customize the schedule. The time specified by Scheduled Switching Time cannot be later than the time specified by Latest Execution Time. Check whether the appropriate events are selected. If the appropriate events are selected, click Save to save the settings. Otherwise, select appropriate events on the Scheduled Event page, and then re-configure the scheduled events.
Periodic switchover time	Important After the periodic switchover time is set, all scheduled events generated from the current time are switched based on the most recent switchover time. For example, if you set the periodic switchover time to 12:00:00 on Tuesday and 12:00:00 on Friday, scheduled events generated from 12:00:00 on Tuesday to 12:00:00 on Friday are switched at 12:00 on Friday. Scheduled events from 12:00:00 on Friday to 12:00:00 next Tuesday are switched at 12:00:00 next Tuesday. In the upper-left corner of the Scheduled Event page, click Global Scheduler. In the Global Scheduler panel, specify the periodic switchover time by Week or Month based on your business requirements. Note You can view the specified periodic switchover time in the upper-right corner of the Scheduled Event page. If you select None, the periodic switchover time is not displayed. Click Save to save the settings.
Instance maintenance window	The default maintenance window is 02:00-06:00. Click the instance ID. On the Basic Information page, you can view the maintenance window in the Specification Information section. You can also click Edit next to Maintenance Window to modify the maintenance window. For more information, see Specify a maintenance window.

Cancel a scheduled event
If the Event Type value of a scheduled event is Minor Version Upgrade, you can click Cancel Scheduled Event in the upper-left corner of the Scheduled Event page to cancel the event.

Causes and impacts of events

Cause	Impact	Description
Instance migration	Transient disconnections	After a scheduled switchover starts, the following impacts take effect on your cluster: Your instance or the data shard in your instance encounters transient disconnections and remains in the read-only state for up to 30 seconds before all data is synchronized. We recommend that you perform the switchover during off-peak hours and make sure that your application is configured to automatically reconnect to your instance. You cannot manage your instances by using DMS or DTS. This impact is temporary.
Minor engine version update	Transient disconnections	After a scheduled switchover starts, the following impacts take effect on your cluster: Your instance or the data shard in your instance encounters transient disconnections and remains in the read-only state for up to 30 seconds before all data is synchronized. We recommend that you perform the switchover during off-peak hours and make sure that your application is configured to automatically reconnect to your instance. You cannot manage your instances by using DMS or DTS. This impact is temporary.
Minor engine version update	Minor version update	Different minor versions or kernel versions have different updates. You must take note of the differences between the current minor version and the minor version to which your instance is upgraded.
Proxy minor version update	Transient disconnections	After a scheduled switchover starts, the following impacts take effect on your cluster: Your instance or the data shard in your instance encounters transient disconnections and remains in the read-only state for up to 30 seconds before all data is synchronized. We recommend that you perform the switchover during off-peak hours and make sure that your application is configured to automatically reconnect to your instance. You cannot manage your instances by using DMS or DTS. This impact is temporary.
Proxy minor version update	Minor version update	Different minor versions have different updates. You must take note of the differences between the current minor version and the minor version to which your proxy nodes are upgraded.
SSL certificate renewal	Transient disconnections	After a scheduled switchover starts, the following impacts take effect on your cluster: Your instance or the data shard in your instance encounters transient disconnections and remains in the read-only state for up to 30 seconds before all data is synchronized. We recommend that you perform the switchover during off-peak hours and make sure that your application is configured to automatically reconnect to your instance. You cannot manage your instances by using DMS or DTS. This impact is temporary.
Major engine version upgrade	Transient disconnections	After a scheduled switchover starts, the following impacts take effect on your cluster: Your instance or the data shard in your instance encounters transient disconnections and remains in the read-only state for up to 30 seconds before all data is synchronized. We recommend that you perform the switchover during off-peak hours and make sure that your application is configured to automatically reconnect to your instance. You cannot manage your instances by using DMS or DTS. This impact is temporary.
Major engine version upgrade	Major version upgrade	Different major versions or kernel versions have different updates. You must take note of the differences between the current major version and the major version to which your instance is upgraded.

Related API operations

Operation	Description
DescribeActiveOperationTaskCount	Queries the number of O&M tasks on an ApsaraDB for MongoDB instance.