2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa