If an O&M event, such as instance migration or version upgrade, needs to be managed, you will receive phone calls, emails, or internal messages. In addition, you are prompted to manage the event after you log on to the ApsaraDB RDS console. You can view the types, regions, and IDs of the RDS instances that are affected by the O&M event, and the cause and impacts of the event. You can also change the scheduled time of switchovers that are triggered by the O&M event.

Prerequisites

A pending O&M event exists.

Note To check whether pending O&M events exist, you can move the pointer over the Notification icon in the upper-right corner of the ApsaraDB RDS console.

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 usingphone 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.

Figure 1. Message Center settings
Message Center settings

Procedure

  1. Log on to the ApsaraDB RDS console.
  2. In the left-side navigation pane, click Event Center. In the top navigation bar, select a region.
    Note If a pending O&M event requires you to schedule a time for the O&M operation, a message appears, which prompts you to schedule the time at your earliest opportunity.
  3. Optional:On the Scheduled Events tab, configure the periodic switching time.
    Note The Set Global Schedule panel provides the global configuration items of proactive O&M events except events to fix high-risk vulnerabilities. After you configure the periodic switching time, the scheduled time of switchovers for newly generated proactive O&M events is automatically changed based on the configured time interval. If you do not configure the periodic switching time, the scheduled time of switchovers for newly generated proactive O&M events is automatically changed based on the maintenance window of your RDS instance. For more information, see Set the maintenance window of an ApsaraDB RDS for MySQL instance.
    1. Click Set Global Schedule.
    2. In the panel that appears, configure the required parameters and click Save.
  4. On the Scheduled Events tab, view the details of the event. To change the switching time of the event, select the RDS instance that you want to manage and click Schedule Event.
    Note The displayed information varies based on the event type.
  5. In the Schedule Event dialog box, configure the scheduled switching time and click OK.
    Note
    • If you select Earliest Execution Time, the system automatically provides the earliest switching date and time for the next O&M operation. After you save the settings, the instance prepares to switch over and enters the Pending state. If you do not select this option, you can customize the date and time.
    • The time that is specified by the Scheduled Disconnection Time parameter cannot be later than the time that is specified by the Set Before parameter.

Causes and impacts of events

Cause Impact Description
Instance migration Transient connections
After a switchover is performed at the scheduled switching time, the following impacts occur:
  • Your RDS instance or the data shard in your RDS instance experiences transient connections and stays 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 RDS instance.
  • You cannot manage your RDS instance by using Data Management (DMS) or Data Transmission Service (DTS). This impact is temporary.
Switchover between primary and secondary instances
SSL certificate update
Backup mode change
Minor engine version update Transient connections
After a switchover is performed at the scheduled switching time, the following impacts occur:
  • Your RDS instance or the data shard in your RDS instance experiences transient connections and stays 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 RDS instance.
  • You cannot manage your RDS instance by using Data Management (DMS) or Data Transmission Service (DTS). This impact is temporary.
Differences between minor engine versions Different minor engine versions have different updates. You must take note of the differences between the current minor engine version and the version to which you want to update. For more information, see the relevant release notes. Release notes are available only for the following services:
Minor version update for proxies Transient connections
After a switchover is performed at the scheduled switching time, the following impacts occur:
  • Your RDS instance or the data shard in your RDS instance experiences transient connections and stays 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 RDS instance.
  • You cannot manage your RDS instance by using Data Management (DMS) or Data Transmission Service (DTS). This impact is temporary.
Differences between minor engine versions Different minor versions have different updates. You must take note of the differences between the current minor version and the minor version to which you want to update
Network upgrade Transient connections
After a switchover is performed at the scheduled switching time, the following impacts occur:
  • Your RDS instance or the data shard in your RDS instance experiences transient connections and stays 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 RDS instance.
  • You cannot manage your RDS instance by using Data Management (DMS) or Data Transmission Service (DTS). This impact is temporary.
Change of virtual IP addresses (VIPs) Some network upgrades may involve cross-zone migrations that change the VIP of your RDS instance. If a client uses a VIP to connect to a cloud database, the connection is interrupted.
Note To prevent transient connections, you must use the endpoint in the form of a domain name that is provided by your RDS instance and disable the DNS cache feature of the application and the server.