My Oracle Support Banner

Replication Lag with Parallel Slave Threads (Doc ID 2491599.1)

Last updated on MARCH 02, 2020

Applies to:

MySQL Server - Version 5.7 and later
Information in this document applies to any platform.

Symptoms

When having a topology of replication such as:

 

Changes

MySQL 5.5 has single threaded slave binlog applier and this often resulted in a bottleneck and caused replication lag to increase.

MySQL 5.6 introduced the DATABASE parallel replication scheme, which considers that any transactions that work on different databases can be executed in parallel on the slave applier.

MySQL 5.7 introduced the LOGICAL_CLOCK parallel replication scheme, extending parallelism to transactions within the same database. Initially it considered that only transactions that committed together on the same binary log group commit could be executed together on the slave, but then that was improved upon to work on intervals of dependencies, reducing the impact of serialization points that were seen at group commit boundaries.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.