Event English Name | Event Type | Subordinate Dimension | Recovery Concept Availability | Event Description | Solution and Suggestion |
MasterHealthCheckError | Abnormal event | TencentDB for MySQL instance dimension | No | The primary instance may be unable to determine whether the current primary instance node service status is active due to high load, maximum number of connections reached, runtime exceptions, network fluctuations, etc. | Node configurations can be increased appropriately to reduce the probability of risks. 1. If you receive a MasterHealthCheckRecovery event, it means that the primary node has recovered, HA switch rollback has occurred, and no actual HA has occurred. 2. If you receive both Switch and SlaveHealthCheckRecovery events, it indicates that HA switch has occurred and recovery succeeded. 3. If you receive a Switch event but do not receive a SlaveHealthCheckRecovery event, it means that HA switch has occurred and the original primary instance has been rebuilt. |
MasterHealthCheckRecovery | Recovery event | TencentDB for MySQL instance dimension | No | Recovery after the database primary node encounters a service exception. | The database MasterHealthCheckError has recovered from the service exception and is now operating normally. |
SlaveHealthCheckError | Abnormal event | TencentDB for MySQL instance dimension | No | The replica instance may be unable to determine whether the current replica instance node service status is active due to high load, maximum number of connections reached, runtime exceptions, network fluctuations, etc. | Node configurations or the number of read-only nodes can be increased appropriately to reduce the probability of risks. 1. If you receive SlaveHealthCheckRecovery, it indicates the replica node has recovered. 2. If you does not receive SlaveHealthCheckRecovery, it indicates that the replica node health check has timed out and been rebuilt. |
SlaveHealthCheckRecovery | Recovery event | TencentDB for MySQL instance dimension | No | 1. Recovery after the database replica node encounters a service exception. 2. The original primary node is abnormal. After the primary-replica switch, the original abnormal primary node recovers as a replica node. | 1. The database SlaveHealthCheckError has recovered from the service exception and is now operating normally. 2. The original MasterHealthCheckError of the database has recovered from the service exception and is now operating normally. |
Was this page helpful?