2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
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)
respondido hace 4 años
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?
respondido hace 3 años
Contenido relevante
- OFICIAL DE AWSActualizada hace 8 meses