Scheduled event

Prerequisites

You have pending maintenance events.

Notes

• Events are categorized into two types based on their urgency:

  • S0 Emergency Level: Risk Remediation: These typically address unexpected scenarios requiring prompt remediation to prevent failures. Notifications for such events may be sent 3 days or more in advance, with a limited window for modifying the scheduled switchover time. Typical scenarios include urgent version replacement upgrades, host exceptions, and SSL Certificate expiration upgrades.

  • S1 Planned Level: System Maintenance: These typically involve low-risk issue remediation or planned software and hardware upgrades. Notifications are usually sent more than 3 days in advance, and users can cancel these events.

• To ensure you receive scheduled notifications for O&M events, you must log on to the Message Hub and ensure the notification method check boxes for ApsaraDB failure or O&M notifications are selected and message recipients are set (we recommend assigning them to database O&M personnel). Otherwise, you will not receive event notifications.Notification methods include text message, email, and internal message. We recommend selecting both text message and email to improve delivery success rates.

  

  Figure 1. Message Center notification settings entry

  

  Figure 2. ApsaraDB notification settings

• To receive immediate updates about O&M events or to build custom O&M automation using an event-driven approach, you can configure system event subscriptions through the Cloud Monitor platform. ApsaraDB pushes CloudMonitor system events for the lifecycle of O&M events, such as subscription, start, completion, and cancellation. For detailed instructions, see Manage Event Subscriptions (Recommended). For a list of subscribable CloudMonitor events, see Appendix 1: CloudMonitor-Related System Events.

  Expand to view a Cloud Monitor event format example.

  {
    "eventId": "c864b30b-7f69-5f04-b0e7-8dfb0eabcfd9", // Event ID. The ID is the same for the same event.
    "product": "RDS",                                  // Product code
    "reason": "Host software/hardware upgrade",        // Event reason
    "extra": {
      "impactZh": "Transient instance disconnection",                           // Event impact
      "impactEn": "Transient instance disconnection",  // Event impact
      "eventCode": "rds_apsaradb_transfer",            // O&M event type code
      "eventNameEn": "Instance migration",             // O&M event name
      "eventNameZh": "Instance migration",                        // O&M event name   
      "switchTime": "2024-09-15T01:30:00+08:00",       // Scheduled switchover time. If a switchover occurs, this is the time of transient instance disconnection.
      "startTime": "2024-09-14T21:30:00+08:00",          // Scheduled start time. The event enters the scheduling queue and waits for execution.
      "cancelCode": "OutOfGoodPerfBySoftHardwareUpgrade", // Cancellation risk code. See Appendix 2: Detailed Reason Codes and Cancellation Risks.
      "detailCode": "HostSoftHardwareUpgrade",            // Detailed reason code. See Appendix 2: Detailed Reason Codes and Cancellation Risks.
      "instanceInfo": ""
    },
    "instanceId": "rm-2ze9d66o65q1g02g6",             // Instance ID
    "eventType": "Maintenance",
    "instanceComment": "rm-2ze9d66o65q1g02g6",        // Instance alias
    "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.