Release Notes
Product Announcements
Chinese Name of Event | English Name of Event | Event Type | Dimension | Recovery Concept Availability | Event Description | Solutions and Suggestions |
Exception in Primary Node Service Test | MasterHealthCheckError | Exception Event | TencentDB for MySQL instance dimension | No | The primary instance may be unable to determine the current primary instance node service status as active due to high load, maximum number of connections reached, runtime exceptions, network fluctuations, etc. | The node configurations can be appropriately added to reduce the probability of risk occurrence. 1. If you receive a MasterHealthCheckRecovery event, it means that the primary node has been recovered, HA has been switched to rollback, 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 has occurred and the original primary instance has been reconstructed. |
Primary Node Service Test Exception Recovery | MasterHealthCheckRecovery | Recovery event | TencentDB for MySQL instance dimension | No | Recovery after the database primary node encounters a service exception. | The service exception (MasterHealthCheckError) on the database primary node has been recovered and is now operating normally. |
Replica Node Service Test Exception | SlaveHealthCheckError | Exception Event | TencentDB for MySQL instance dimension | No | The replica instance might be unable to determine the current replica instance node service status as active due to high load, the maximum number of connections reached, runtime exceptions, and network fluctuations, etc. | Node configurations or the number of read-only nodes can be appropriately increased to reduce the probability of risk occurrence. 1. If you receive SlaveHealthCheckRecovery, it indicates that the replica node has been recovered. 2. If you have not received SlaveHealthCheckRecovery, it indicates that the replica node test has timed out and is being reconstructed. |
Replica Node Service Test Exception Recovery | 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 switchover, the originally abnormal primary node is recovered as the replica node. | 1. The service exception (SlaveHealthCheckError) on the database replica node has been recovered and is now operating normally. 2. The service exception (MasterHealthCheckError) on the database original primary node has been recovered and is now operating normally. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback