O&M event management - Hologres - Alibaba Cloud Documentation Center

Hologres O&M events notify you of potential threats or scheduled operations affecting your instances. These events include architecture upgrades, system maintenance, and agent version upgrades. Respond to them promptly based on your business needs to avoid impacts on instance availability and enhance stability.

View O&M events

Log on to the Hologres console.
In the top menu bar, select a region.
In the left navigation pane, click O&M Event Management.
On the O&M Event Management page, click the Scheduled Events tab or the Historical Events tab to view all O&M events for the instances under your account. For more information about event types, see Event descriptions.
- Scheduled Events: Lists planned or ongoing events.
- Historical Events: Lists completed events, including both successful and failed events.

Configure O&M event notifications

When Hologres initiates an event, the system automatically sends notifications via methods such as text message and email to the associated Alibaba Cloud account. The event is also pushed to System Event in CloudMonitor. Create alert rules for the event based on your business needs to stay informed of its progress. For more information, see Use system event alerts.

Event descriptions

The following table describes the event types pushed by Hologres, the corresponding O&M operations, and their business impacts.

Event type

Description

O&M operation

Business impact

System maintenance

Common reasons include the following:

The instance requires an upgrade due to critical issues or security bugs.
An automatic upgrade is triggered because the instance exceeds the product lifecycle policy.
A compute cluster is migrated.
A backend O&M restart is required due to hardware or network issues.
The instance configuration is changed.

Common O&M operations include the following:

Restarting the instance
Performing a cold upgrade of the instance version
Performing a hot upgrade of the instance version

The impacts of the O&M operations are as follows:

Restarting the instance: Your services on the instance are briefly interrupted. The interruption typically lasts several minutes.
Performing a cold upgrade: The instance is stopped. Downtime varies based on instance size and typically lasts several minutes.
Performing a hot upgrade: Write operations are suspended, but read operations are unaffected. The duration of the write suspension varies based on instance size but is typically within 10 minutes. A brief service interruption occurs during this process.

Agent version upgrade

Common reasons include the following:

The agent performs a version upgrade for the instance in the backend.

Common O&M operations include the following:

Performing a cold upgrade of the instance version
Performing a hot upgrade of the instance version

The impacts of the O&M operations are as follows:

Performing a cold upgrade: The instance is stopped. Downtime varies based on instance size and typically lasts several minutes.
Performing a hot upgrade: Write operations are suspended, but read operations are unaffected. The duration of the write suspension varies based on instance size but is typically within 10 minutes. A brief service interruption occurs during this process.

Architecture upgrade

Common reasons include the following:

The underlying technical architecture is upgraded.

Common O&M operations include the following:

Migrating the instance to a different zone

The impacts of the O&M operations are as follows:

Migrating the instance to a different zone: This operation is equivalent to a hot upgrade. During the migration, write operations are suspended, but read operations are unaffected. The duration of the write suspension varies based on instance size but is typically within 10 minutes. A brief service interruption occurs during this process.

Note

The basic configuration of the instance remains unchanged after the zone migration. However, monitor network connectivity promptly.