Overview
For more information, see Scheduled events of database services.
Event types
The steps inside the red boxes in the flowchart have an impact on the service.
Type | Process | Impact | Cause | O&M suggestion |
Instance migration |  | Experiences transient connections and remains in the read-only state for 30 seconds. | The machine that hosts the instance is experiencing issues. | S0: Migrate data to the new instance at the earliest opportunity. |
Minor version update |  | Experiences transient connections and remains in the read-only state for 30 seconds. | Earlier minor versions of Redis contain risks or security vulnerabilities. | S1: Update the minor version of the instance. After the minor version is updated, the new version remains compatible with earlier versions. |
Proxy minor version update | Update proxy nodes in small, incremental batches | Experiences transient connections that last for several seconds. | Earlier minor versions of proxy nodes contain risks or security vulnerabilities. | S1: Update the minor version of proxy nodes for the instance at the earliest opportunity. After the minor version is updated, the new version remains compatible with earlier versions. |
SSL certificate renewal |
| Experiences transient connections and remains in the read-only state for 30 seconds. | The SSL certificate has expired. | S0: Renew the certificate at the earliest opportunity. After the certificate expires, access to the instance may fail. Do not cancel the certificate. |
Major version upgrade |  | Experiences transient connections and remains in the read-only state for 60 seconds. | The major version of the instance is outdated and no longer maintained. | S1: Upgrade the major version at the earliest opportunity. After the major version is upgraded, the new version remains compatible with earlier versions. |
Severity levels:
[S0 = critical severity] Risk fixing: In most cases, events at this level involve unexpected issues that require immediate attention to prevent system failures. Notifications for S0 issues are sent at least three days in advance, and the window for modifying the scheduled switchover time is small. Typical scenarios include urgent fixes such as emergency version replacements or upgrades, host exception fixing, and SSL certificate renewal upon expiration.
[S1 = high severity] Scheduled system maintenance: In most cases, events at this level involve low-risk issue resolution or scheduled upgrades and updates for software or hardware. Notifications for S1 events are sent more than three days in advance, and users have the option to cancel the events when necessary.
FAQ
For more information, see FAQ about scheduled events.
Related API operations
API operation | Description |
Queries the information about multiple proactive O&M events. | |
Modifies the scheduled switchover time of O&M events for an instance. | |
Cancels the O&M events of an instance. |