All Documents
Current Document

Recommend

Container Engine Virtual Private Cloud Standard Storage Service

Found 0 result in total

Content is empty

If you don't find the content you expect, please try another search term

Documentation

Auto Scaling

View more results
Document title with current keyword not found
Directory
Expand AllFold All Up
No products found with this keyword
Documentation Auto Scaling Troubleshooting Scale-out failure

Scale-out failure

Last updated：2020-06-24 12:01:54

Causes and solutions for scale-out failures

Cause Description Solution
The launch configuration is invalid. The launch configuration is invalid because the custom image specified in the launch configuration has been deleted. On the details page of the launch configuration, the resources deleted by mistake are marked red. Change the launch configuration of the scaling group.
The Server Load Balancing (SLB) instance is deleted. After the SLB instance is deleted, new Kingsoft Cloud Elastic Compute (KEC) instances cannot be registered with the SLB instance. Attach an existing SLB instance to the scaling group.
The listener is deleted. The listener is deleted but new KEC instances need a listener to distribute requests. Configure an existing listener for the scaling group.
Resources are sold out. The pay-as-you-go KEC instances are sold out in the availability zone, and cannot be purchased automatically or manually. N/A
The instance type does not exist. The instance type specified in the launch configuration is invalid or not sold any more. Change the launch configuration of the scaling group.
The associated Virtual Private Cloud (VPC) or subnet is deleted. The VPC or subnet specified for the scaling group has been deleted, so KEC instances cannot be created. Configure an existing VPC or a subnet for the scaling group.
A backend error occurs. N/A Suspend the scale-out activity.
The associated security group (firewall) is deleted. The security group (firewall) specified for the scaling group has been deleted, so KEC instances cannot be created. Configure an existing security group (firewall) for the scaling group.

Impacts of an invalid launch configuration on a scaling group

  1. The scaling group does not stop working immediately when the launch configuration becomes invalid.

  2. Normal scale-in activities can still be triggered.

    • The limits on KEC instances, including the maximum, minimum, and average numbers, still take effect.

    • Scale-out activities cannot be triggered.
On this page
Previous:Troubleshooting
Next:Invalid launch configuration
Pure ModeNormal Mode

Pure Mode

Click to preview the document content in full screen
Feedback