- 最新
- 投票最多
- 评论最多
Hello.
When a failover occurs, the RDS instance that was originally the writer instance becomes the reader instance.
Therefore, there is no particular problem as long as the reading process is performed on the reader endpoint.
It is a good idea to have multiple reader instances to reduce the downtime of read processing during failover.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.AuroraHighAvailability.html#Aurora.Managing.FaultTolerance
In Aurora MySQL 2.10 and higher, you can improve availability during a failover by having more than one reader DB instance in a cluster. In Aurora MySQL 2.10 and higher, Aurora restarts only the writer DB instance and the reader instance to which it fails over. Other reader instances in the cluster remain available during a failover to continue processing queries through connections to the reader endpoint.
Hi,
If you want to automatically create a new read instance (to avoid re-use of failed one), you can use the RDS-EVENT-0013 in AWS EventBridge to trigger a Lambda that will automatically create a new and fresh read instance.
See doc for events: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.Messages.html#USER_Events.Messages.instance
Best,
Didier
相关内容
- AWS 官方已更新 3 年前
However if the original writer was having issue, what good to make it the new reader?