I have a strange situation with MySQL replication lag happening on relatively idle servers.

Slave shows no symptoms of IO saturation (according to top, iotop or iostat), no symptoms of CPU saturation. If I do SHOW SLAVE STATUS at regular intervals, it seems, that slave spends 99% of it's time at two events:

  • Waiting for slave workers to process their queues
  • Waiting for dependent transaction to commit (happening most often).

The problem is that the database is about 1Tb in size and it's not easy experimenting with it. Both master and slave are Xeon E5 with SSD RAID10 storage. Investigation showed no lagging of slave IO thread. Everything looks like slave SQL thread is constantly waiting for some event to complete before replaying next transaction from log.

Replication type used is row-based. We tried to switch to slave_parallel_type = LOGICAL_CLOCK and set slave_parallel_workers = 24 but with no success. We see no server resource over-utilization. All metrics show that the server is mostly idle. log_slow_slave_statements shows nothing. innodb_flush_log_at_trx_commit = 2 to prevent fsyncs() on small transactions (not that it was necessary because we are nowhere near iops limit but we wanted to try something).

Putting additional load to server does not affect replication lag.

Database being replicated contains about 95% of InnoDB tables and some TokuDB tables.

This situation started about several months ago at a time point none can remember. Despite of the fact, that it is a visible point in Grafana for us, we can't remember or find something in logs that could bring us closer to the problem cause.

MySQL server version is 5.7 by Percona.

migrated from serverfault.com Dec 22 '17 at 15:44

This question came from our site for system and network administrators.

  • Just a stupid question from my side: Did you check networking (e.g. packet loss or very high latencies)? And could you please run "dstat" on the master and slave for 10 seconds and update your question accordingly? Maybe this brings some additional information (although I doubt it, since you already checked iostat etc.). – Valentin Dec 12 '17 at 8:45
  • @Valentin This cannot be network problem, because we can see, that all binlogs are delivered to a slave in time. But are not processed. – Vladislav Rastrusny Dec 12 '17 at 13:50
  • 1
    Can you add a SHOW FULL PROCESSLIST on the slave showing all the workers status? – Matthew Ife Dec 12 '17 at 14:47
  • It sounds like it is a SQL problem, not a resource problem. The message indicates that you have have an uncommitted transaction (that is presumably preventing your replication from completing). So the replication process is probably blocked because it's waiting for a SQL commit. It might also be related to a full transaction log - so perhaps check that first? – user228546 Dec 15 '17 at 18:59
  • 1
    You could also try this to find the offending queries: select * from INFORMATION_SCHEMA.PROCESSLIST where db = 'TheMySQLDB'; – user228546 Dec 15 '17 at 23:23

Check these two server parameters (my.cnf):

  1. slave_pending_jobs_size_max should be same or more than the value of max_allowed_packet https://dev.mysql.com/doc/refman/8.0/en/replication-options-slave.html#sysvar_slave_pending_jobs_size_max

  2. slave_transaction_retries value should be twice of slave_parallel_workers.

Your Answer


By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.