What Should I Do If a Node Pool Is Abnormal?

Error

The node pool cannot be deleted.

Delete the node pool again. If the node pool still cannot be deleted, submit a service ticket and delete the node pool.

QuotaInsufficient

The node pool cannot be scaled out due to insufficient quota.

Submit a service ticket and increase the quota.

SoldOut

The underlying resources are insufficient.

Update the node pool configuration and select other available resources.

ConfigurationInvalid

The ECS group does not exist (ServerGroupNotExists).

The ECS group to which the node pool belongs is not present. This may be because you manually deleted the ECS group.

1. Log in to the CCE console. In the navigation pane, choose Nodes. In the right pane, click the Node Pools tab and click the name of the target node pool. Click the Overview tab, click Expand, and check the ECS group to which the node pool belongs.
2. Log in to the ECS console. In the navigation pane, choose Elastic Cloud Server > ECS Group and see if the target ECS group is present.
3. If the ECS group is not present, log in to the CCE console. In the navigation pane, choose Nodes, click the Node Pools tab, locate the row containing the target node pool, and click Update. In the Advanced Settings area, unbind or change the ECS group.

MaxNodeCountReached

The number of expected nodes in the current node pool or scaling group has reached the maximum allowed limit.

• Manually add nodes to the node pool or scaling group as needed. If the expected number of nodes in a node pool or scaling group reaches the maximum allowed limit, auto scaling will no longer be triggered for that node pool or scaling group. However, this does not affect manual scale-out operations.
• Choose Nodes in the navigation pane, click the Node Pools tab in the right pane, locate the row containing the target node pool, click Auto Scaling, and change the value of Nodes.

  Or simply disable auto scaling of the node pool or scaling group.