Check the health of KEC instances

When you create a scaling group, you must specify the expected number of Kingsoft Cloud Elastic Compute (KEC) instances. The expected number of KEC instances specifies the initial number of KEC instances in the scaling group when the scaling group is created. The number of KEC instances in the scaling group will be maintained between the maximum number and minimum number that you set.

Note:

• Min. Node Number: the minimum number of KEC instances in the scaling group. If the number of KEC instances in the scaling group is less than the minimum number, Auto Scaling automatically adds KEC instances until the number of KEC instances equals the minimum number.

• Expected number of KEC instances: the initial number of KEC instances in the scaling group when the scaling group is created.

• Max. Node Number: the maximum number of KEC instances in the scaling group. If the number of KEC instances in the scaling group is greater than the maximum number, Auto Scaling automatically removes KEC instances until the number of KEC instances equals the maximum number.

To ensure that KEC instances run properly in a scaling group, Auto Scaling periodically checks the health of the KEC instances. When an unhealthy KEC instance is detected, Auto Scaling terminates the KEC instance and launches a new KEC instance to replace the unhealthy one.

• Replace an unhealthy KEC instance

  When a KEC instance is marked as unhealthy in a scaling group, Auto Scaling immediately launches a new instance to replace the unhealthy one. However, if removal protection is enabled for the unhealthy KEC instance, Auto Scaling will not replace it with a new KEC instance.