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.
A:
“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/
A
Correct answer is A
Option A IS CORRECT
A.
You will need to delete the Read Replica and create a new one to replace it.
FAQ doesn’t say that we need to delete Replica…! But given all the answer choices A appears to be the correct choice.
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?
You may find in some cases that your Amazon RDS for MySQL Read Replica(s) aren’t able to receive or apply updates from their source Multi-AZ DB instance after a Multi-AZ failover. This may be due to MySQL binlog events not being flushed to disk at the time of the failover. It is important that you configure your MySQL DB instance for replication as described in the Amazon RDS User Guide.