If your ApsaraDB RDS instance has an event pending to be processed, the ApsaraDB RDS console notifies you of the event, so you can handle the event at your earliest opportunity.

You can receive text messages, voice messages, and emails that notify you of pending events such as instance migration and version upgrade events. In addition, after you log on to the ApsaraDB RDS console, you are prompted to manage the pending events. You can view the types, regions, processes, precautions, and affected instances of the pending events. You can also change the value of the Scheduled Disconnection Time parameter.

Prerequisites

A pending event is found, which is an O&M event.

Note If pending events are found, you can see notification badges on the Pending Events button in the upper-right corner of the ApsaraDB RDS homepage.

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. Event notifications are sent by usingphone calls, emails, internal messages, or the ApsaraDB for Redis console. To use this feature, log on to theMessage 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. Click Events Center in the left-side navigation pane or click Pending Events upper-right corner of the ApsaraDB RDS homepage,.
    Note If a pending event requires you to schedule the time to handle the event, a message appears, which prompts you to schedule the time at your earliest opportunity.
  3. On the Pending Events page, select the type and region of the event that you want to handle.
    Note The content of the notification for an event varies based on the value of Event Type. The notification provides the process and precautions for the event.
  4. View details about the event in the instance list. If you want to change the value of Scheduled Disconnection Time, select an RDS instance and click Specify Disconnection Time. In the dialog box that appears, specify the time and click OK.
    Note
    • The information that is displayed for an event varies based on the type of the event.
    • The value of Scheduled Disconnection Time cannot be later than the time that is displayed in the Set Before column.

Causes and impacts of events

Cause Impact type Impact description
Instance migration Transient connections
From the time specified by Scheduled Disconnection Time,the RDS instance is subject to the following impacts:
  • The RDS instance or its database shards experience transient connections and stay in the read-only state for up to 30 seconds until all data is synchronized. We recommend that you perform the operation during off-peak hours and make sure that your application is configured to automatically reconnect to your database system.
  • The RDS instance cannot work as expected for Data Management (DMS) or Data Transmission Service (DTS). After the operation is complete, the RDS instance is automatically recovered.
Primary/secondary switchover
SSL certificate update
Backup mode change
Minor engine version update Transient connections
From the time specified by Scheduled Disconnection Time,the RDS instance is subject to the following impacts:
  • The RDS instance or its database shards experience transient connections and stay in the read-only state for up to 30 seconds until all data is synchronized. We recommend that you perform the operation during off-peak hours and make sure that your application is configured to automatically reconnect to your database system.
  • The RDS instance cannot work as expected for Data Management (DMS) or Data Transmission Service (DTS). After the operation is complete, the RDS instance is automatically recovered.
Differences between minor engine versions Different minor engine versions provide different features. Before you update the minor engine version of the RDS instance, you must take note of the differences between the previous and new minor engine versions. For more information, see the release notes of minor engine versions.
Proxy version upgrade Transient connections
From the time specified by Scheduled Disconnection Time,the RDS instance is subject to the following impacts:
  • The RDS instance or its database shards experience transient connections and stay in the read-only state for up to 30 seconds until all data is synchronized. We recommend that you perform the operation during off-peak hours and make sure that your application is configured to automatically reconnect to your database system.
  • The RDS instance cannot work as expected for Data Management (DMS) or Data Transmission Service (DTS). After the operation is complete, the RDS instance is automatically recovered.
Differences between proxy versions Different proxy versions provide different features. Before you upgrade the proxy version of the RDS instance, you must take note of the differences between the previous and new proxy versions.
Network upgrade Transient connections
From the time specified by Scheduled Disconnection Time,the RDS instance is subject to the following impacts:
  • The RDS instance or its database shards experience transient connections and stay in the read-only state for up to 30 seconds until all data is synchronized. We recommend that you perform the operation during off-peak hours and make sure that your application is configured to automatically reconnect to your database system.
  • The RDS instance cannot work as expected for Data Management (DMS) or Data Transmission Service (DTS). After the operation is complete, the RDS instance is automatically recovered.
VIP connection errors Network upgrades may involve cross-zone data migration. In this case, the virtual IP address (VIP) of the RDS instance changes. If a database client uses a VIP to connect to the RDS instance, the connection is interrupted.
Note We recommend that you use a domain name to connect to the RDS instance and disable the DNS cache of your application and the DNS cache of the server on which your application runs.