How do I query and configure scheduled events? - ApsaraDB for HBase

For scheduled O&M events of ApsaraDB for HBase, you can be notified by phone calls, emails, or internal messages. You can also be notified in the ApsaraDB for HBase console. The scheduled O&M events include minor version updates. You can view the type, region, procedure, affected instances, considerations, and default switchover time of a scheduled event. You can also modify the scheduled switchover time.

Usage notes

In most cases, Alibaba Cloud notifies you at least three days before system maintenance events such as minor version updates are executed. Notifications for high-risk vulnerability fixes are sent within three days before execution due to the urgency of these events.

Alibaba Cloud sends notifications by using phone calls, emails, internal messages, or messages in the ApsaraDB for HBase console. To ensure that you can receive notifications, you must log on to Message Center, select ApsaraDB Fault or Maintenance Notifications, and then specify a contact. We recommend that you specify an O&M engineer as the contact. If you do not specify a contact, you cannot receive notifications.

Procedure

Log on to the ApsaraDB for HBase console.
In the left-side navigation pane, choose Event Center > Scheduled Event.
On the Scheduled Event page, view the details about the events.
The event details include the instance ID, region, event type, cause, impact on business, scheduled switchover time, and status. For more information about the causes of events and the impacts of events on business, see the Causes and impacts of events section of this topic.
You can perform the following operations on an event:
- Change the scheduled switchover time.
  You can use the default switchover time or change the scheduled switchover time. The priority of the scheduled switchover time is higher than the priority of the default switchover time.
  1. On the Scheduled Event page, select one or more events.
  2. In the upper-left corner of the event list on the Scheduled Event page, click Config Scheduled Event.
  3. In the Add Scheduled Event panel, set the scheduled switchover time.
    If you want to immediately perform a switchover, select Earliest Execution Time. After you confirm the settings, the system immediately prepares for the switchover. If the preparation is already complete, the system immediately performs the switchover.
    Note
    The time specified by Scheduled Switching Time cannot be later than the time specified by Latest Execution Time.
  4. Check whether the events that you selected are the events for which you want to apply the scheduled switchover time.
    If the events that you selected are the events for which you want to apply the scheduled switchover time, click OK.
    Otherwise, select the events for which you want to apply the scheduled switchover time in the Scheduled Event list and reconfigure the scheduled switchover time.
- Cancel the scheduled switchover for an event.
  You can cancel the scheduled switchover only for a minor version update event. You can select a minor version update event and click Cancel Scheduled Event.

Causes and impacts of events

Cause

Impact

Description

Minor version update

Transient connections

At the scheduled switchover time, your instances may experience the following impacts. We recommend that you perform the switchover during off-peak hours and make sure that your applications are configured with a reconnection mechanism.

Single-zone instance: One switchover is performed. During the switchover, your instances or the data shards in your instances experience transient connections and stay in the read-only state for up to 30 seconds before all data is synchronized.
Multi-zone instance: Two switchovers are performed. During the switchovers, your instances or the data shards in your instances experience transient connections and stay in the read-only state for up to 30 seconds before all data is synchronized. The second switchover switches the master node to the primary zone. This prevents an increase in access latency that may occur when the master node is in the secondary zone.

Differences between minor versions

Different minor versions (kernel versions) have different updates. For more information, see Release notes for minor versions.