Amazon Aurora V1 inaccessible after scaling for long periods

0

Sometimes after a scaling operation on Aurora Serverless v1 (mySQL) and the database becomes completely inaccessible for a considerable amount of time. Today the database was not available for 2 hours (i.e. accepting connections) until it recovered.

Sometimes recovery can be manually triggered by a "force-scale" up or down in the console.

We had to created a new Aurora Serverless v1 from an snapshot as Point in Time recovery was not available either. The new cluster was twice unavailable again for about 2 minutes with messages like

The DB cluster has scaled from 8 capacity units to 4 capacity units, but scaling wasn't seamless for this reason: An internal error occurred.

or

The DB cluster has scaled from 4 capacity units to 8 capacity units, but scaling wasn't seamless for this reason: An internal error occurred.

It is set to roll back the capacity change if a scaling point cannot be found and even if connections were dropped, I would expect being able to re-connect, but not being locked out without any options for periods of time. Since it's serverless, we don't have any insights or even the ability to restart and the message "An internal error occurred" is rather vague and unhelpful.

How can this downtime be prevented?

RobertB
asked 2 years ago997 views
2 Answers
0

I suggest creating a support ticket for this issue, they will be able to take a look at what was happening and help with the remediation.

Regards

AWS
answered 2 years ago
0

This is exactly the type of situation that's addressed in Aurora Serverless v2: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/

In Serverless v2, the scaling doesn't have to wait for a quiet point; doesn't disrupt any existing connections, transactions, or running queries; doesn't introduce any hiccups in connecting - it's very careful not to decrease the max_connections setting even when scaling down.

Serverless v2 is available for MySQL 8.0-compatible and PostgreSQL 13, 14, and 15-compatible. For precise minimum versions, see https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.Aurora_Fea_Regions_DB-eng.Feature.ServerlessV2.html#Concepts.Aurora_Fea_Regions_DB-eng.Feature.ServerlessV2.amy and https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.Aurora_Fea_Regions_DB-eng.Feature.ServerlessV2.html#Concepts.Aurora_Fea_Regions_DB-eng.Feature.ServerlessV2.apg

I know this question is a couple of years old. Posting this answer for the benefit of users who are still thinking of Serverless v1 when they hear about "Aurora Serverless".

johrss
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions