- Mais recentes
- Mais votos
- Mais comentários
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
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".
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 3 meses