1 Answer
- Newest
- Most votes
- Most comments
0
Looks like you are running a single instance cluster with no read replicas. If the underlying HW fails, it will try to bring up the instance on a new host and has to to crash recovery and can take up to 10 min. Your application should be connecting to the cluster endpoint and that will not change. To avoid this downtime you can add a replica which reduces the downtime to a few seconds instead of minutes, what happens in the background is that it will failover to the replica and make it a writer instance. The cluster end point will remain the same.
** PS : If this answers your question and helps you resolve the issue, please accept the answer **
answered 2 years ago
Relevant content
- asked a month ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you for your response. Could you elaborate on a few points? The console only lists a reader and a writer endpoint. What is the "cluster endpoint"? <somename>-cluster.cluster-ro-<some id>.<region>.rds.amazonaws.com <somename>-cluster.cluster-<some id>.<region>.rds.amazonaws.com Can you comment on the frequency of recovery events? Bad luck?