My Read Replica appears “stuck” after a Multi-AZ failover and is unable to obtain or apply updates from the
source DB Instance. What do I do?
A.
You will need to delete the Read Replica and create a new one to replace it.
B.
You will need to disassociate the DB Engine and re associate it.
C.
The instance should be deployed to Single AZ and then moved to Multi- AZ once again
D.
You will need to delete the DB Instance and create a new one to replace it.
Explanation:
Q: My Amazon RDS for MySQL Read Replica appears “stuck” after a Multi-AZ failover and is unable to obtain
or apply updates from the source DB Instance. What do I do? … To resolve the current issue, you will need to
delete the Read Replica and create a new one to replace it. “
https://aws.amazon.com/rds/faqs/
Q: My Read Replica has fallen significantly behind its source DB Instance. What should I do?
As discussed in the previous questions, “inconsistency” or lag between a Read Replica and its source DB Instance is common with asynchronous replication. If an existing Read Replica has fallen too far behind to meet your requirements, you can delete it and create a new one with the same endpoint by using the same DB Instance Identifier and Source DB Instance Identifier as the deleted Read Replica. Keep in mind that the re-creation process will be counter-productive at small lag levels (e.g. under five minutes of lag), and should be used with prudence (i.e. only when the Read Replica is significantly behind its source DB Instance). Also keep in mind that replica lag may naturally grow and shrink over time, depending on your source DB Instance’s steady-state usage pattern.
Scaling the DB Instance class of a Read Replica may reduce replication lag in some cases, particularly if your source DB Instance class is larger than your Read Replica DB Instance class. However, Read Replicas are not guaranteed to work in all cases. There may be scenarios and usage patterns where a Read Replica can never catch up with its source after initial creation, or otherwise remains too far behind its source to meet your use case requirements.
0
0
A
0
0