ApsaraDB for MongoDB notifies you of upcoming O&M events — such as instance migrations and version upgrades — and lets you control when the associated switchover occurs. Use this page to view event details, configure the switchover time, and cancel eligible events.
Prerequisites
Before you begin, ensure that you have:
At least one scheduled O&M event in ApsaraDB for MongoDB
In the top navigation bar of the ApsaraDB for MongoDB console, click Scheduled Events to see how many scheduled events are pending.
Usage notes
Regular events (instance migrations, version upgrades): you are notified at least three days before the event occurs.
High-risk vulnerability fixes: you are notified three or fewer days before execution due to urgency.
Notifications are delivered by phone call, email, internal message, and through the ApsaraDB for MongoDB console.
To choose how you receive notifications, go to Message Center, enable Message CenterApsaraDB Fault or Maintenance Notifications, and specify a contact. Designate an O&M engineer as the contact.
View event details
Log on to the ApsaraDB for MongoDB console.
In the left-side navigation pane, click Scheduled Events.
ImportantIf a pending event requires you to schedule a switchover time, a prompt appears asking you to do so at the earliest opportunity.
On the Scheduled Event page, review the following columns: Event Type, Cause, Business Impact, Start At, Scheduled Disconnection Time, Set Before, Status, Database Type, and Cancelable.
For a description of each event type's cause and business impact, see Causes and impacts of events.
Configure the switchover time
Three switchover time modes are available, listed in descending order of priority:
| Mode | Priority | When to use |
|---|---|---|
| Scheduled switchover time | Highest | One-off events where you need precise control over the exact date and time |
| Periodic switchover time | Medium | Recurring maintenance — consolidates all upcoming events into fixed weekly or monthly slots rather than handling each event individually |
| Instance maintenance window | Lowest | Default fallback; applies automatically when no scheduled or periodic time is set |
Set a scheduled switchover time
On the Scheduled Event page, select one or more events.
In the upper-left corner, click Add Scheduled Event.
In the Schedule Event panel, set the switchover time:
To use the earliest available time, select Earliest Execution Time. The system populates the date and time automatically. After saving, the selected instances enter the Pending state.
To choose a custom time, clear Earliest Execution Time and enter the date and time in the Scheduled Switching Time field. The time cannot be later than Latest Execution Time.
Verify that the correct events are selected:
If the correct events are selected, click Save.
If not, return to the Scheduled Event page, select the appropriate events, and repeat the steps above.
Set a periodic switchover time
Use this mode to consolidate all upcoming events into regularly scheduled slots — for example, every Tuesday and Friday — rather than handling each event individually.
After you set a periodic switchover time, all scheduled events generated from that point forward are executed at the next upcoming slot. For example, if the periodic time is set to 12:00 on Tuesday and 12:00 on Friday:
Events that occur between Tuesday 12:00 and Friday 12:00 are switched at Friday 12:00.
Events that occur between Friday 12:00 and the following Tuesday 12:00 are switched at the following Tuesday 12:00.
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.
The configured periodic time appears in the upper-right corner of the Scheduled Event page. If you select None, the periodic switchover time is not displayed.
Click Save.
Use the instance maintenance window
If you do not set a scheduled or periodic switchover time, events fall back to the instance maintenance window. The default window is 02:00–06:00.
To view or change the maintenance window:
Click the instance ID.
On the Basic Information page, locate the Specification Information section.
Click Edit next to Maintenance Window to modify the window.
For details, see Specify a maintenance window.
Cancel a scheduled event
Only Minor Version Upgrade events can be canceled. To cancel one, click Cancel Scheduled Event in the upper-left corner of the Scheduled Event page.
Causes and impacts of events
Events that cause transient disconnections
The following events cause your instance or data shard to experience transient disconnections and enter a read-only state for up to 30 seconds while data synchronizes. DMS and DTS cannot manage your instances during this period (this impact is temporary).
Schedule these switchovers during off-peak hours and make sure your application is configured to automatically reconnect to the instance.
| Cause | Impact |
|---|---|
| Instance migration | Transient disconnections |
| Minor engine version update | Transient disconnections |
| Proxy minor version update | Transient disconnections |
| SSL certificate renewal | Transient disconnections |
| Major engine version upgrade | Transient disconnections |
Events that do not cause disconnections
| Cause | Description |
|---|---|
| Minor version update | Different minor versions and kernel versions include different updates. Review the differences between the current version and the target version before the event. |
| Proxy minor version update | Different minor versions have different updates. Review the differences between the current minor version and the minor version to which your proxy nodes are upgraded. |
| Major version upgrade | Different major versions and kernel versions include different updates. Review the differences between the current version and the target version before the event. |
Related API operations
| Operation | Description |
|---|---|
| DescribeActiveOperationTaskCount | Queries the number of O&M tasks on an ApsaraDB for MongoDB instance. |