You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In very large clusters with many target groups, we may want to 'batch' terminations so that we do not work on more than N instances at the same time.
When we get a hook we should start the worker that sends heartbeat, but possibly queue it until a slot is available.
For example,
With 500+ target groups, and 20 concurrent terminations, lifecycle-manager might have a hard time making progress, however if we only work on 5 instances at a time, performance of overall systems might be better.
We should take a controller flag --deregister-max-parallel and hold-off on deregistering any instance over N in parallel
The text was updated successfully, but these errors were encountered:
In very large clusters with many target groups, we may want to 'batch' terminations so that we do not work on more than N instances at the same time.
When we get a hook we should start the worker that sends heartbeat, but possibly queue it until a slot is available.
For example,
With 500+ target groups, and 20 concurrent terminations, lifecycle-manager might have a hard time making progress, however if we only work on 5 instances at a time, performance of overall systems might be better.
We should take a controller flag
--deregister-max-parallel
and hold-off on deregistering any instance over N in parallelThe text was updated successfully, but these errors were encountered: