- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Purchase Guide
- Get Started
- Operation Guide
- Use Limits
- Operation Overview
- Instance Management and Maintenance
- Instance Upgrade
- Expanding Instance
- Database Proxy
- Account Management
- Database Management Console (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Best Practice
- Usage Specifications of TencentDB for MySQL
- Configuring Application Automatic Reconnection
- Impact of Modifying MySQL Master Instance Parameters
- Limits on Automatic upgrade from MyISAM to InnoDB
- Creating VPCs for TencentDB for MySQL
- Enhancing Business Load Capacity with TencentDB for MySQL
- Building LAMP Stack for Web Application
- Building Drupal Website
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Backup APIs
- DescribeBackupConfig
- ModifyBackupConfig
- DeleteBackup
- DescribeBackups
- DescribeBinlogs
- CreateBackup
- DescribeSlowLogs
- DescribeDataBackupOverview
- DescribeBinlogBackupOverview
- DescribeBackupSummaries
- DescribeBackupOverview
- ModifyBackupDownloadRestriction
- DescribeBackupDownloadRestriction
- ModifyLocalBinlogConfig
- DescribeLocalBinlogConfig
- Task APIs
- Security APIs
- Data Import APIs
- Parameter APIs
- Instance APIs
- DescribeDBInstanceGTID
- CloseWanService
- SwitchForUpgrade
- CreateDBInstanceHour
- DescribeDBInstanceCharset
- ModifyDBInstanceVipVport
- ModifyDBInstanceProject
- IsolateDBInstance
- UpgradeDBInstanceEngineVersion
- DescribeDBInstances
- InitDBInstances
- DescribeDBInstanceRebootTime
- OpenWanService
- UpgradeDBInstance
- ModifyDBInstanceName
- DescribeDBZoneConfig
- RestartDBInstances
- OpenDBInstanceGTID
- DescribeDBSwitchRecords
- DescribeDBInstanceConfig
- ModifyAutoRenewFlag
- ModifyInstanceTag
- DescribeTagsOfInstanceIds
- ModifyTimeWindow
- DescribeTimeWindow
- DeleteTimeWindow
- AddTimeWindow
- OfflineIsolatedInstances
- ReleaseIsolatedDBInstances
- ModifyRoGroupInfo
- DescribeRoGroups
- BalanceRoGroupLoad
- DescribeDBInstanceInfo
- DescribeRoMinScale
- CreateRoInstanceIp
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- StopReplication
- StartReplication
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- ModifyNameOrDescByDpId
- Database APIs
- Account APIs
- Rollback APIs
- Monitoring APIs
- Log APIs
- Database Audit APIs
- Database Proxy APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Purchase Guide
- Get Started
- Operation Guide
- Use Limits
- Operation Overview
- Instance Management and Maintenance
- Instance Upgrade
- Expanding Instance
- Database Proxy
- Account Management
- Database Management Console (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Best Practice
- Usage Specifications of TencentDB for MySQL
- Configuring Application Automatic Reconnection
- Impact of Modifying MySQL Master Instance Parameters
- Limits on Automatic upgrade from MyISAM to InnoDB
- Creating VPCs for TencentDB for MySQL
- Enhancing Business Load Capacity with TencentDB for MySQL
- Building LAMP Stack for Web Application
- Building Drupal Website
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Backup APIs
- DescribeBackupConfig
- ModifyBackupConfig
- DeleteBackup
- DescribeBackups
- DescribeBinlogs
- CreateBackup
- DescribeSlowLogs
- DescribeDataBackupOverview
- DescribeBinlogBackupOverview
- DescribeBackupSummaries
- DescribeBackupOverview
- ModifyBackupDownloadRestriction
- DescribeBackupDownloadRestriction
- ModifyLocalBinlogConfig
- DescribeLocalBinlogConfig
- Task APIs
- Security APIs
- Data Import APIs
- Parameter APIs
- Instance APIs
- DescribeDBInstanceGTID
- CloseWanService
- SwitchForUpgrade
- CreateDBInstanceHour
- DescribeDBInstanceCharset
- ModifyDBInstanceVipVport
- ModifyDBInstanceProject
- IsolateDBInstance
- UpgradeDBInstanceEngineVersion
- DescribeDBInstances
- InitDBInstances
- DescribeDBInstanceRebootTime
- OpenWanService
- UpgradeDBInstance
- ModifyDBInstanceName
- DescribeDBZoneConfig
- RestartDBInstances
- OpenDBInstanceGTID
- DescribeDBSwitchRecords
- DescribeDBInstanceConfig
- ModifyAutoRenewFlag
- ModifyInstanceTag
- DescribeTagsOfInstanceIds
- ModifyTimeWindow
- DescribeTimeWindow
- DeleteTimeWindow
- AddTimeWindow
- OfflineIsolatedInstances
- ReleaseIsolatedDBInstances
- ModifyRoGroupInfo
- DescribeRoGroups
- BalanceRoGroupLoad
- DescribeDBInstanceInfo
- DescribeRoMinScale
- CreateRoInstanceIp
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- StopReplication
- StartReplication
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- ModifyNameOrDescByDpId
- Database APIs
- Account APIs
- Rollback APIs
- Monitoring APIs
- Log APIs
- Database Audit APIs
- Database Proxy APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
Feature 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 above.
- Kernel version: MySQL 5.7 20180530 and above.
- Kernel version: MySQL 5.6 20170830 and above.
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.
Use Instructions
Set the slave_parallel_type parameter to the new value TABLE to enable this feature.
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* | DATABASE | DATABASE/TABLE/LOGICAL_CLOCK | The level of parallel replication at the replica node. |
Yes
No
Was this page helpful?