2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Looks to me like this is intended behavior: you have enabled "Force scaling the capacity to the specified values when the timeout is reached", which means that connections which block a scaling event due to active (probably long-running) transactions will be terminated when the scaling timeout is reached. If you want the scaling event to wait for all active transactions to finish, you'll need to disable that setting...
-Kevin J (PM for Aurora PostgreSQL)
répondu il y a 4 ans
0
Hi, I am currently having the very same issue.
But at least for me, if I disable the option to "force autoscale", I get an error in the Aurora events log with the message: "Scaling point wasn't found".
How to proceed?
répondu il y a 3 ans
Contenus pertinents
- demandé il y a 15 jours
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans