CODEWITHSUNDEEP
amazon-web-servicesamazon-rdsread-replicationmulti-az
stowns
stowns

Reputation: 321

How to handle read-replica connection pool during Multi-AZ fail-over in AWS RDS?

As I understand it, I can use a Multi-AZ RDS deployment for HA and add Read Replicas to improve my read capacity and performance. In able to leverage Read Replicas I will need to maintain a separate connection pool with-in my Application strictly for read operations. However, from what I've read it appears that Read Replication is broken when a Multi-AZ RDS fails over to the standby instance. If this is true:

  1. How do manage the Read Connection Pool in my Application? ie) will the dns addresses of the read replicas change and therefor require application code changes to update the Connection Pool?
  2. Should I have read replicas already created for the standby instance or can I re-associate the existing read replicas with the standby?
  3. Will the Read Replicas continue to function during failure and effectively serve my Application stale data until I update the connection pool?

Upvotes: 1

Views: 1076

Answers (0)

Related Questions