tencent cloud

Feedback

Parallel Replication

Last updated: 2022-03-02 21:34:46

    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.
  • 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.
  • Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support