2 Answers
- Newest
- Most votes
- Most comments
0
When Serverless needs to scale, it looks for a safe scaling point for 5 min, if it can not ( because of long running transactions) , then it either rolls back the scaling or if you have forced scaling enabled, it will kill current in-flight transactions and force a scaling. If it can not find a scaling point, then its quite possible that the current ACUs are unable to handle the new load and this can lead to a restart ( cpu brownout). So that could explain the restart when it goes from 4 to 8. however I see no reason for a restart during scale down. So its recommended that you should open a ticket with support.
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 2 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- How do I end long-running queries in my Amazon RDS for PostrgreSQL or Aurora PostgreSQL DB instance?AWS OFFICIALUpdated 2 months ago