Autoscaling: use labels instead of draining nodes #5339
Labels
a:autoscaling
autoscaling service in simcore's stack
a:director-v2
issue related with the director-v2 service
Milestone
After extensive testing from @YuryHrytsuk about the fact that starting sim4life is a bit slow could be related to the fact that nodes are drained and undrained.
The current explanation is that when a node is drained, all the containers running there are removed, and all the networks are also removed.
An alternative would be to keep the node active all the time and use a docker label/docker constraint to prevent unwanted containers to start on these machines.
Autoscaling currently works like so:
This change would affect the second part:
is-drained=true
Advantages
Requirements:
is-drained=true
is setThe text was updated successfully, but these errors were encountered: