1 Answers
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 6 days ago
Relevant questions
How to connect to RDS aurora MYSQL private DB using Boto3?
asked 2 months agoSwitch Reserved Instance from Aurora to mySQL
asked 2 years agoAurora mysql: Started cross AZ failover to DB instance event
asked 7 months agoAWS RDS Aurora MySql Serverless: ft_min_word_len is not being recognized
asked 4 months ago[RDS, Aurora MySQL] Frequent "Recovery of the DB instance has started. Recovery time will vary with the amount of data to be recovered."
asked 6 days agoHow can we find out when were the binary logs of a MySQL RDS instance created?
asked 3 months agoMove RDS MySQL 5.6.40 database to Aurora Serverless
asked 3 years agoInstability in RDS MySQL db after increasing storage space
asked 2 years agoUnable to configure Multi AZ deployment for existing Aurora MySQL
Accepted Answerasked 5 months agoDoes Recovery of DB instance run automatically?
Accepted Answerasked a month 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?