2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
I would recommend you to open a support case to troubleshoot the issue since you are getting an Internal Error.
In addition to that, please note that for scaling operations Aurora Serverless v1 first tries to identify a scaling point, a moment when no queries are being processed. Aurora Serverless might not be able to find a scaling point for the following reasons:
- Long-running queries
- In-progress transactions
- Temporary tables or table locks
répondu il y a 2 ans
0
In addition to the above, the "Minimum capacity", "Pre-warming" and "Scale-blocking operations" sections of this Best practices for working with Amazon Aurora Serverless blog post are probably helpful.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a 14 jours
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans