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
Parallel Replication
Last updated: 2024-07-22 11:30:52
Overview
Prior to MySQL 5.6, the source node syncs binlogs and the replica node replays binlogs, both in the single-thread mode. MySQL 5.6 and later versions support the DATABASE/LOGICAL_CLOCK parallel replication scheme, but the granularity is too large to achieve expected parallel replication in many cases.
Tencent Cloud's TXSQL kernel team has optimized the parallel replication scheme. Table parallel replication is now supported, improving parallelism and reducing source-replica delay.
Supported Versions
Kernel version: MySQL 8.0 20201230 and later.
Kernel version: MySQL 5.7 20180530 and later.
Kernel version: MySQL 5.6 20170830 and later.
Use Cases
This feature is suitable for use cases where optimizing the parallelism of some loads can speed up the binlog replay at the replica node, thus reducing the source-replica delay.
Instructions
For MySQL 5.6 and 5.7, you can enable this feature by setting the
slave_parallel_type parameter to the newly added value TABLE. MySQL 8.0 does not support the TABLE mode.
Additionally, the cdb_slave_thread_status table is added to the information_schema database to display the thread status of the replica node.Parameter | Effective Immediately | Type | Default Value | Valid Values/Value Range | Description |
slave_parallel_type | Yes | char* | SCHEMA | SCHEMA/TABLE | The level of parallel replication on the replica node. SCHEMA: Replication events of different schemas can be executed in parallel. TABLE: Replication events of different tables can be executed in parallel. |
Parameter | Effective Immediately | Type | Default Value | Valid Values/Value Range | Description |
slave_parallel_type | Yes | char* | LOGICAL_CLOCK | DATABASE/TABLE/LOGICAL_CLOCK | The level of parallel replication on the replica node. DATABASE: Replication events of different databases can be executed in parallel. TABLE: Replication events of different tables can be executed in parallel. LOGICAL_CLOCK: Replication events of the same logical clock on the host can be executed in parallel. |
Parameter | Effective Immediately | Type | Default Value | Valid Values/Value Range | Description |
slave_parallel_type | Yes | char* | LOGICAL_CLOCK | DATABASE/LOGICAL_CLOCK | The level of parallel replication on the replica node. DATABASE: Replication events of different databases can be executed in parallel. LOGICAL_CLOCK: Replication events of the same logical clock on the host can be executed in parallel. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No