This topic summarizes the system events supported by RDS Custom, including scheduled maintenance events and unexpected maintenance events, and provides handling suggestions for each system event.
Format of RDS Custom event codes and CloudMonitor event names
To help you establish automated maintenance mechanisms through system events, RDS Custom system events are synchronized to CloudMonitor. The RDS Custom event codes and CloudMonitor event names for the same event follow specific naming formats:
RDS Custom event code: Includes information about the event cause and impact on resources, in the format
<event cause>.<impact on resources>.CloudMonitor event name: Includes information about the resource type, event cause, impact on resources, and event status, in the format
<resource type>:<event cause>.<impact on resources>:<event status>.
Not all RDS Custom event codes and CloudMonitor event names include all information. For example, the CloudMonitor event name Disk:ErrorDetected:Executing indicates that disk corruption has been detected, so information about subsequent impact on resources is not needed.
Scheduled O&M events
When you restart an instance from within the operating system, the maintenance actions corresponding to the event cannot take effect. Therefore, the instance restart operations mentioned in this topic refer to operations performed through the RDS Custom console or by calling API operations. For more information, see Restart an instance or RebootRCInstance.
Event code | Event name | Event level | CloudMonitor event name | Event description and impact | Handling suggestions |
SystemMaintenance.Reboot | Instance restart due to system maintenance | Critical |
| Alibaba Cloud detects potential software or hardware failure risks on the host where the RDS Custom instance is deployed. These risks may cause the RDS Custom instance to restart. The risk has not directly become a failure. This system event is sent 24 to 48 hours before the scheduled system maintenance time. Note Failure risks include the following:
| Manually restart the instance. Note We recommend that you pay attention to the status changes of the event. If the event status does not change after you restart the instance, the event response failed and the risk is not eliminated. We recommend that you restart the instance at a suitable time later (preferably more than 12 hours after this operation) to avoid the risk. |
SystemMaintenance.Stop | Instance stop due to system maintenance | Critical |
| Alibaba Cloud detects potential software or hardware failure risks on the host where the RDS Custom instance is deployed. These risks may cause the RDS Custom instance to shut down and stop. The risk has not directly become a failure. This system event is sent 24 to 48 hours before the scheduled system maintenance time. | |
SystemMaintenance.Redeploy | Instance redeployment due to system maintenance | Critical |
| Alibaba Cloud detects potential software or hardware failure risks on the host where the RDS Custom instance is deployed. These risks may cause the RDS Custom instance to be redeployed. The risk has not directly become a failure. This system event is sent 24 to 48 hours before the scheduled system maintenance time. Important Instances that use local SSD disks or local HDD disks will have their data disks reinitialized, and data on the local disks will be deleted. | We recommend that you complete the preparations, including modifying the /etc/fstab configuration file and backing up data. Then, choose one of the following response methods based on your needs:
Note We recommend that you pay attention to the status changes of the event. If the event status does not change after you redeploy the instance, the event response failed and the risk is not eliminated. We recommend that you redeploy the instance at a suitable time later (preferably more than 12 hours after this operation) to avoid the risk. |
SystemFailure.Redeploy | Instance redeployment due to system error | Critical |
| When Alibaba Cloud identifies that an RDS Custom instance needs to be redeployed due to software or hardware failures on the underlying host, this system event is sent immediately. Note Only instances that depend on host hardware support this type of event, such as instances with local disks attached or instances that support SGX encrypted computing. | We recommend that you complete the preparations, including modifying the /etc/fstab configuration file and backing up data. Then, choose one of the following response methods based on your needs:
|
SystemMaintenance.CleanReleasedDisks | Instance needs to clean up configuration information of released disks | Warning |
| When Alibaba Cloud identifies that the operating system of an RDS Custom instance contains configuration information for one or more disks that were released due to overdue payment, this system event is sent. | We recommend that you choose a suitable time to authorize Alibaba Cloud to clean up the configuration information of released disks. Important Alibaba Cloud will shut down the instance at the specified time you authorize, clean up the disks, and then start the instance again. |
Unexpected O&M events
Event code | Event name | Event level | CloudMonitor event name | Event description and impact | Handling suggestions |
SystemFailure.Reboot | Instance restart due to system error | Critical |
| When Alibaba Cloud identifies that an RDS Custom instance is restarted due to unexpected software or hardware failures (such as CPU or memory hardware damage) on the underlying host, this system event is sent immediately. | We recommend that you wait for the instance to automatically restart, and then check if the instance and applications are functioning normally. During the restart process, Alibaba Cloud will migrate the instance to another healthy host. |
InstanceFailure.Reboot | Instance needs to restart due to operating system error | Critical |
| When Alibaba Cloud identifies that an RDS Custom instance has crashed due to internal operating system issues, including out-of-memory, blue screen, freezing, continuous serial port log printing, or kernel panic, this system event is sent immediately. | We recommend that you wait for the instance to automatically restart, and then check if the instance and applications are functioning normally. You can enable the Kdump service in the operating system to troubleshoot the crash cause and avoid similar issues in the future. For more information, see How to enable the Kdump service for Linux instances. |
SystemFailure.Stop | Instance stop due to system error | Critical |
| When Alibaba Cloud identifies that an RDS Custom instance is shut down due to software or hardware failures (such as CPU or memory hardware damage) on the underlying host, this system event is sent immediately. | We recommend that you wait for the instance to automatically stop, and then start the instance. When you start the instance, Alibaba Cloud will migrate it to another healthy host. |
SystemFailure.Delete | Bill automatically canceled due to instance creation failure | Critical |
| When Alibaba Cloud identifies that an RDS Custom instance was ordered successfully but failed to be created, this system event is sent immediately. | We recommend that you wait for the system to automatically release the instance, which typically occurs within five minutes after creation failure. Note If you have already paid for the order, you will receive a refund after the instance is released. |
InstanceFailure.PerformanceImpact | Instance performance degraded due to instance error | Warning |
| When an unexpected exception occurs within the instance (such as a GuestOS kernel hang) that deg instance's performance, this system event is sent immediately. | We recommend that you log on to the instance to identify and resolve the exception, and then monitor the status of this system event. If the system event is no longer reported, it indicates that the performance degradation has been resolved. |