| 2 | system user | | NULL | Connect | 779612 | Waiting for master to send event | NULL | | 3 | system user | | NULL | Connect | 4215 | Reading event from the relay log | NULL |And the replication latency continue to grow: "Seconds_Behind_Master: 4234"
When we look at MySQL dashboard to check on database activity graph (see below), its doing only avg 170 inserts/second.
MySQL config for replication slave hosts can be configured to behave differently, the benefit is to help assist with replication catch-up. In this scenario we changed the value of innodb_flush_log_at_trx_commit to 2 from default 1. After this change, significant increase in db activity was observed, replication lag started to reduce sharply, and replication caught up with MySQL database under 5 mins, see below db activity graph: