ApsaraDB RDS:Scheduled event

Prerequisites

You have pending maintenance events.

Notes

• Events are classified into two levels of urgency:

  • [S0 Urgent] Risk Remediation: Typically involves unexpected issues requiring immediate action to prevent service failures. Notifications for these events are sent three days or less in advance, and the window for rescheduling the switchover time is shorter. Examples include urgent version replacement and upgrades, host failure recovery, and upgrades for expiring SSL certificates.

  • [S1 Scheduled] System Maintenance: Involves low-risk issue fixes or planned software and hardware upgrades. Notifications for these events are usually sent more than three days in advance, and you can cancel the event.

• To receive notifications for scheduled O&M events, log on to the Message Center, and select the notification methods and configure contacts for ApsaraDB Fault or Maintenance Notifications. We recommend adding your database O&M personnel as contacts. Otherwise, you will not receive event notifications.Notification methods include Email and Internal Messages. We recommend you select Email to ensure delivery.

  In the upper-right corner of the console, click the bell icon. Then, in the Internal Message Notifications panel, click Message Settings.

  Figure 1. Accessing Message Settings

  

  Figure 2. Notification settings for ApsaraDB

• To receive real-time updates on O&M events or implement custom, event-driven automation, configure system event subscriptions in CloudMonitor. ApsaraDB pushes system events to CloudMonitor for each stage of the O&M event lifecycle, such as Scheduled, In Progress, Succeeded, and Canceled. For more information, see Manage event subscriptions (Recommended). For a list of subscribable CloudMonitor events, see Appendix 1: CloudMonitor-related system events.

  Expand to view a sample CloudMonitor event.

  {
    "eventId": "c864b30b-7f69-5f04-b0e7-8dfb0eabcfd9", // A unique ID for the event.
    "product": "RDS",                                  // The service code.
    "reason": "Host software/hardware upgrade",        // The reason for the event.
    "extra": {
      "impactEn": "Transient instance disconnection",  // The impact of the event.
      "eventCode": "rds_apsaradb_transfer",            // The code for the O&M event type.
      "eventNameEn": "Instance migration",             // The name of the O&M event.
      "switchTime": "2024-09-15T01:30:00+08:00",       // The scheduled switchover time. A transient instance disconnection may occur at this time.
      "startTime": "2024-09-14T21:30:00+08:00",          // The time when the event is queued for execution.
      "cancelCode": "OutOfGoodPerfBySoftHardwareUpgrade", // The cancellation risk code. For details, see Appendix 2: Detailed cause codes and cancellation risks.
      "detailCode": "HostSoftHardwareUpgrade",            // The detailed cause code. For details, see Appendix 2: Detailed cause codes and cancellation risks.
      "instanceInfo": ""
    },
    "instanceId": "rm-2ze9d66o65q1g02g6",             // The instance ID.
    "eventType": "Maintenance",
    "instanceComment": "rm-2ze9d66o65q1g02g6",        // The alias of the instance.
    "instanceType": "Instance",
    "publishTime": "2024-09-10T16:01:47+08:00"
  }

Procedure

1. Log on to the ApsaraDB RDS console.

2. In the left-side navigation pane, click Event Center.

   Note

   For maintenance events that require you to schedule a time, a pop-up window appears to remind you to schedule the time as soon as possible.

3. Optional: On the Scheduled events page, configure a recurring time window to manually schedule events.

   Note

   Recurring time window settings is a global configuration for proactive database maintenance events, excluding emergency risk remediation events. After you set a recurring window, the scheduled switching time for new maintenance events automatically falls within this window. If you do not set a recurring window, the time is automatically set within the instance's maintenance window.

   1. Click Recurring time window settings.

   2. In the panel that appears, set the recurring time and click Save.

4. On the Scheduled events page, view the details of an event. For an event that is in the Planned state, select the instance for which you want to modify the event time and click Schedule Event.

   Note

   The information that is displayed varies based on the event type. The information on the actual page takes precedence.

5. In the Schedule Event dialog box, set a scheduled switching time and click OK.

   Note

   • Select Earliest Execution Time to automatically schedule the switchover for the earliest possible time. After you click Save, the instance starts to prepare for the switchover and enters the Pending state. If you clear this option, you can specify a custom date and time.

   • The scheduled switching time cannot be later than the latest action time.

Event causes and impacts

FAQ

Q: Are RDS maintenance events automatically performed? Can I cancel a task?

A: Yes. To ensure instance stability, scheduled events are performed automatically and cannot be canceled. You can, however, change the scheduled switching time. We recommend that you schedule the event during off-peak hours and ensure your application has a reconnection mechanism. For more information about how to change the scheduled switching time, see the Procedure section of this topic.