2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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
beantwortet vor 2 Jahren
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.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren