tencent cloud

TencentDB for MySQL

문서TencentDB for MySQL

Primary-Replica Switch Position Information Event

Download
포커스 모드
폰트 크기
마지막 업데이트 시간: 2024-11-27 15:20:14
This document introduces the event related to the primary-replica switch position information when TencentDB for MySQL is used, as well as corresponding handling suggestions.
Note:
For guidance on setting event alarms, see Setting Event Alarms.

Primary-Replica Switch Position Information Event and Handling Suggestions

This event is applicable to the following instance types: two-node and three-node. Cluster edition and single-node instances are not supported.
English Event Name
Event Type
Dimension
Recovery Message Provided
Event Description
Solution and Suggestion
SwitchBinlogPOS
Exception event
TencentDB for MySQL instance dimension
No
There is a lot of information about this event. Obtain the complete information through the connector or API callbacks.
Position changes during an instance's route switch (including HA switch, upgrade, and other scenarios) and log file information:
New Master Binlog Position (new primary position after a route switch): {$position}. In HA scenarios, it is the position of the original replica instance, and in upgrade scenarios, it is the position of the new primary instance.
New Master Binlog File (new primary log file name after a route switch): {$file}.
Old Master Binlog Position (old primary position before a route switch): {$position}.
Old Master Binlog File (old primary log file name before a route switch): {$file}.
After a primary-replica switch, send position information before and after the switch.
Note:
If you receive an alarm from Short Message Service (SMS)/message center/email, the corresponding event alarm push content is:
New primary position: {New Master Binlog Position}, file: {New Master Binlog File}.
Old primary position: {Old Master Binlog Position}, file: {Old Master Binlog File}.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백