By using AWS re:Post, you agree to the Terms of Use
/RDS Read Replica Lag/

RDS Read Replica Lag

0

I have an db.m5.8xlarge RDS MySQL database in the us-east-2 region with 15k Max IOPS and a read replica of the same size and specifications in us-east-1.

When our business day starts our replica lag starts. It generally reached about 6000-8000 second on any given business day.

While this is a high transaction database, this level of lag makes using the read replica for anything other than a straight back up impossible.

I have spent hours researching and trying to tune the MySQL settings to get this replica lag under control.

Does anyone else have any experience solving this problem?

I am running out of ideas.

Thank you.

1 Answers
2

Have you looked into configuring parallel apply on the read replica? By default MySQL replication uses single threaded apply. So if your workload on the source database uses high concurrent connections, these can be serialized on the read replica unless you configure parallel apply. All workloads do not necessarily tend to parallelize as well as others so your mileage might vary, but that is something you can try.

https://dev.mysql.com/doc/refman/8.0/en/replication-options-replica.html see: replica-parallel-workers

answered a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions