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
(INFO) Collective decision: -1
(WARNING) Consensus was to scale down - but number of servers in scaling group (10) exceeds the number of healthy nodes in load balancer 135461 (6). NOT scaling down!
This feature is preventing nodes not ready yet to have time to connect to the CLBs, BUT if for some reasons they don't, these servers stays live and stops autoscale to scale down.
We should have a sort of check to see if the server has been ACTIVE but NOT-CONNECTED to the CLBs for more than X time. Maybe... 30 minutes?
This parameter should be a variable so customer can change this accordingly, but I guess 30 minutes should be a safe default.
The text was updated successfully, but these errors were encountered:
@thtieig as discussed - I think servers failing to provision properly and monitoring for that event is a solution best solved outside of rax-autoscaler.
(INFO) Collective decision: -1
(WARNING) Consensus was to scale down - but number of servers in scaling group (10) exceeds the number of healthy nodes in load balancer 135461 (6). NOT scaling down!
This feature is preventing nodes not ready yet to have time to connect to the CLBs, BUT if for some reasons they don't, these servers stays live and stops autoscale to scale down.
We should have a sort of check to see if the server has been ACTIVE but NOT-CONNECTED to the CLBs for more than X time. Maybe... 30 minutes?
This parameter should be a variable so customer can change this accordingly, but I guess 30 minutes should be a safe default.
The text was updated successfully, but these errors were encountered: