1 回答
- 最新
- 投票最多
- 评论最多
0
Hi there I understand that you created a read only-only aurora replica cluster to offload intense queries. It is expected to have replica lag since binlog replication is asynchronous If nothing is happening on the master [1], the replica will wait for until the master to sent event hence the event that you see. The replica is only active when there is changes to apply[2]. Additionally, it is best practice that the size of the replica be equal to the master instance.
I hope the above information is helpful.
References:
[1]https://aws.amazon.com/premiumsupport/knowledge-center/rds-mysql-high-replica-lag/
[2] https://dev.mysql.com/doc/refman/8.0/en/replica-io-thread-states.html
已回答 2 年前
相关内容
- AWS 官方已更新 1 年前