Skip to Main Content

MySQL Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Replication Lag in 8.0-32

Henrique GarciaMar 6 2026

Hello everyone!

I'd like to share a scenario I'm facing in MySQL 8.0-32 that I didn't experience when using MySQL 5.7-20.

I updated a client a year ago, and I've been experiencing some replication lag.

I've already identified tables that receive large amounts of data and unusable indexes from the (sys) database.

I'd like another perspective on MySQL variables. Currently, on the primary table I use:

Binlog_format = Mixed
binlog_transaction_dependency_tracking = Commit_order
binlog_row_image = Full

And from the documentation I've read, I see the possibility of modifying it to:

Binlog_format = ROW
binlog_transaction_dependency_tracking = WriteSet
binlog_row_image = Minimal.

On the secondary table, I've already optimized it for multitasking replication.

replica_parallel_workers = 24
replica_parallel_type = LOGICAL_CLOCK
replica_preserve_commit_order = OFF
sync_binlog = 0
relay_log_recovery = 1
innodb_flush_log_at_trx_commit = 2

Could you clarify my doubts?

Comments
Post Details
Added on Mar 6 2026
1 comment
62 views