EC2 Spot Fleet Interruption behavior with Capacity rebalance 'Launch before Terminate' strategy
While requesting a fleet, I select Maintain request type with termination behavior Hibernation and then choose Capacity rebalance with "Launch before Terminate" Replacement strategy .. The "Launch before Terminate" option in the console describes it as "Replacement instances will be launched and instances marked for rebalance will be automatically terminated after the termination delay " if this strategy always terminates is there any significance of what is chosen as the interruption behavior ?
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello,
When employing the "Launch before Terminate" replacement strategy alongside a capacity rebalance, the choice of interruption behaviour has minimal impact, as instances flagged for the termination will proceed with termination after the specified delay period, regardless of the selected interruption behaviour.
In other words, the interruption behaviour doesn't change the result when using "Launch before Terminate". The marked instances will terminate after the delay to ensure available replacement capacity. The selection only impacts what state the instances enter temporarily during the delay period, but they will terminate in the end regardless
Thanks
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa