TencentDB for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Database Architecture
- Database Instance
- Kernel Features
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Parallel Query
- Security Features
- Stability Features
- Purchase Guide
- Getting Started
- Connecting to MySQL Instance
- Database Audit
- Audit Rule Template
- MySQL Cluster Edition
- Maintenance Management Instance
- Operation Guide
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Database Proxy Kernel Features
- Database Proxy Management
- Automatic Read/Write Separation Feature
- Connection Pool Feature
- Other Features
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Restoring Database from Backup File
- Monitoring and Alarms
- Operation Logs
- Practical Tutorial
- Calling MySQL APIs in Python
- White Paper
- Performance White Paper
- Performance Test Report
- Troubleshooting
- Connections
- API Documentation
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- Database Proxy APIs
- Database Audit APIs
- Security APIs
- Account APIs
- Backup APIs
- Database APIs
- Monitoring APIs
- Log-related API
- FAQs
- Backup
- Connection and Login
- Instance Upgrade
- Performance and Memory
- Service Agreement
- Reference
Primary-Replica Switch Position Information Event
Last updated: 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:
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}.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No