1. The elastic resource limit has reached the minimum instance count. If further scale-in is required, consider adjusting the minimum instance count.Cause: The scale-in rule was triggered, but the current number of elastic nodes is less than the minimum number of nodes.Solution: If further scale-in is required, reset the minimum node count.
2. The elastic resource limit has exceeded the maximum instance count. If further scale-out is required, consider adjusting the maximum instance count.Cause: The scale-out rule was triggered, but the current number of elastic nodes has reached the maximum instance count.Solution: If further scale-out is required, reset the maximum node count.
3. There is no scaling specification set, so scale-out is not possible. You can try adding specifications and then retry.
Cause: As shown above, an auto-scaling rule has been triggered, but no node specification has been added in the Console > Auto Scaling > Scaling Specification Management.Solution: Click Add Specification in the top-right corner and select the desired node specification.
4. If resources are insufficient, try switching to a specification with sufficient resources or submit a ticket to contact us.Cause: The scale-out rule was triggered, but the selected model’s resources in the current AZ are insufficient.Solution: Reconfigure with a node specification that has sufficient resources.
5. The current retry time is too short; it is recommended to extend the retry duration.
Cause: During the time window from the trigger time to the retry expiration time of the time-based scaling rule, other automatic scaling processes were in progress within the cluster, preventing the current time-based scaling rule from being executed.
Solution: Edit the rule and appropriately extend the expiration retry time to ensure the rule can be executed.
6. The account balance is insufficient, and the scale-out cannot proceed.Cause: The scale-out rule was triggered, but there were insufficient funds when placing the order.Solution: Go to the Cost Center to top up your account.
7. No elastic resources currently meet the conditions for scale-in.
Cause: The scale-in rule was triggered, but there are currently no elastic node resources available, or all nodes are set for scheduled destruction.
Solution: If you need to continue scaling in the nodes scheduled for destruction, you can choose to scale in manually.
8. The cluster is not in a scalable status, so the scale-out is not possible.
Cause: The scale-out rule was triggered, but the current cluster is in a non-operational status such as installing components or scaling out, making it unable to perform the scale-out operation.
Solution: You can perform a manual scale-out or edit the rule to appropriately extend the retry timeout, ensuring the rule can be executed.
9. The cluster is in a scale-out cooldown period and cannot trigger scale-out temporarily. It is recommended to adjust the cooldown time for the scaling rules.
Cause: The scale-out rule was triggered, but the cluster is currently in another scaling cooldown period, so the rule cannot be executed.
Solution: You can shorten the cooldown time of other rules or extend the retry expiration time of the current scale-out rule.
