Monitored DCS Events
Introduction
Event monitoring provides event data reporting, query, and alarm reporting. You can create alarm rules for both system events and custom events. When specific events occur, Cloud Eye generates alarms for you.
Namespace
SYS.DCS
Monitored Events
| Event Name | Event ID | Event Severity | Description | Solution | Impact | Dimension |
|---|---|---|---|---|---|---|
| Full synchronization during online migration retry | migrationFullResync | Minor | During an online migration retry, full synchronization is triggered because incremental synchronization cannot be performed. | Check whether full synchronization retries are triggered repeatedly, whether the source instance is connected, and whether it is overloaded. If full synchronization retries are triggered repeatedly, contact O&M personnel. | The migration task is interrupted from the source instance, and a full synchronization retry is triggered. As a result, the CPU usage of the source instance may increase sharply. | dcs_instance_id |
| Master/Standby failover | masterStandbyFailover | Minor | The master Redis node is abnormal, promoting the replica node as the master. | Check whether services are self-healed. If applications are not restored, restart them. | Persistent connections to the instance will be interrupted. | dcs_instance_id |
| Memcached master/standby failover | memcachedMasterStandbyFailover | Minor | The master Memcached node is abnormal, promoting the standby node as the master. | Check whether services are self-healed. If applications are not restored, restart them. | Persistent connections to the instance will be interrupted. | dcs_memcached_instance_id |
| Abnormal Redis node status | redisNodeStatusAbnormal | Major | The Redis node status is abnormal. | Check whether services are affected. If yes, contact O&M personnel. | If the master node is abnormal, an automatic failover is performed. If a replica node is abnormal and the client directly connects to the replica node for read/write splitting, read operations will be abnormal. | dcs_instance_id |
| Redis node status recovered | redisNodeStatusNormal | Major | The Redis node becomes normal. | Check whether services are restored. If applications cannot reconnect, restart them. | An exception recovery event will occur. | dcs_instance_id |
| Synchronization failure in data migration | migrateSyncDataFail | Major | An online migration task fails. | Reconfigure the migration task and try again. If the fault persists, contact O&M personnel. | Data migration fails. | dcs_instance_id |
| Abnormal Memcached instance status | memcachedInstanceStatusAbnormal | Major | The Memcached node status is abnormal. | Check whether services are affected. If yes, contact O&M personnel. | The Memcached instance status is abnormal, and the instance may be inaccessible. | dcs_memcached_instance_id |
| Memcached instance status recovered | memcachedInstanceStatusNormal | Major | The Memcached node becomes normal. | Check whether services are restored. If applications cannot reconnect, restart them. | An exception recovery event will occur. | dcs_memcached_instance_id |
| Instance backup failure | instanceBackupFailure | Major | The DCS instance fails to be backed up, possibly due to an OBS access failure. | Perform a manual backup. | The automatic backup fails. | dcs_instance_id |
| Abnormal instance node restart | instanceNodeAbnormalRestart | Major | A DCS instance node restarts unexpectedly upon an exception. | Check whether services are self-healed. If applications are not restored, restart them. | Persistent connections to the instance will be interrupted. | dcs_instance_id |
| Long-running Lua scripts terminated | scriptsStopped | Warning | Long-running Lua scripts are automatically terminated. | Optimize Lua scrips to prevent execution timeout. | The execution of Lua scripts takes a long time and is forcibly interrupted. If the execution of Lua scripts takes a long time, the entire instance will be blocked. | dcs_instance_id |
| Automatic node restart | nodeRestarted | Warning | Generally, when Lua scripts have been running for a long time and write operations have been performed, the node is automatically restarted to terminate the scripts. | Check whether services are self-healed. If applications are not restored, restart them. | Persistent connections to the instance will be interrupted. | dcs_instance_id |
| Bandwidth auto scaling triggered | bandwidthAutoScalingTriggered | Warning | Bandwidth auto scaling is triggered when the instance bandwidth usage reaches the upper limit. | Check the services on this instance. | The instance bandwidth is used up, triggering auto scaling. Additional bandwidth will be billed. | dcs_instance_id |
| Specifications auto scaling triggered | specAutoScalingTriggeredSuccess | Warning | The instance specifications are scaled successfully. | Check the services on this instance. | The instance is scaled up. Check its information. | dcs_instance_id |
| Specifications auto scaling failed | specAutoScalingTriggeredFail | Critical | The instance specifications fail to be scaled. | Auto scaling failed. Contact technical support. | The instance fails to be scaled up. Log in to the console to check whether services are affected. | dcs_instance_id |
Dimensions
| Key | Value |
|---|---|
| dcs_instance_id | Redis instance ID. Obtain this value by referring to Listing Monitored Objects on Primary Dimensions. |
| dcs_memcached_instance_id | Memcached instance ID. Obtain this value by referring to Listing Monitored Objects on Primary Dimensions. |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
