Cooldown Period for a Newly Added Node
After a node is added to a node pool that is enabled with auto scaling during a scale-out, autoscaler will not delete the node during the cooldown period when the next auto scaling is triggered.
In auto scaling scenarios, autoscaler parses and selects the auto scaling policies for the clients.
Value Range
Greater than or equal to 0
Default Value
0
Modifiable
Yes
Scope
CCE standard and CCE Turbo clusters
Suggestions
If services have not been running for long and nodes are being added in batches, configure a proper scale-in cooldown period for the nodes. This prevents the newly added nodes from being removed before they bear the next batch of service traffic due to a low resource allocation rate.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot