All Documents
Current Document

Content is empty

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

Documentation

Auto Scaling FAQs

Last updated:2021-05-21 17:42:57

1. What is the cooldown period?

The cooldown period is a period during which Auto Scaling cannot execute any new scaling activities after Auto Scaling completes a scaling activity to add or remove Kingsoft Cloud Elastic Compute (KEC) instances. The cooldown period ranges from 120 to 99999 seconds.

2. When I manually add KEC instances to a scaling group, does Auto Scaling need to wait for the cooldown period to complete before it adds these KEC instances?

No. Auto Scaling does not need to wait for the cooldown period to complete to add manually added KEC instances to a scaling group.

3. Is Auto Scaling free of charge?

Yes. You can use Auto Scaling for free. However, you must pay for the KEC instances that are automatically or manually added at the normal price.

4. How can I increase the maximum number of KEC instances in a scaling group?

You can set the maximum number of KEC instances in a scaling group to 10 at most. If you want a scaling group to support more KEC instances, submit a ticket.

5. What type of applications does Auto Scaling support?

Applications running on KEC instances in Auto Scaling must be stateless and support resource scale-out. Auto Scaling can automatically release KEC instances. Therefore, do not store status information such as sessions and relevant data such as database data and logs on the KEC instances in scaling groups. Otherwise, the data is lost when the KEC instances are released.

If your application needs to store status or log information on KEC instances, you can store the information on independent KEC instances.

6. What requirements does a KEC instance need to meet before it can be manually added to a scaling group?

A KEC instance must meet the following requirements before it can be manually added to a scaling group:

  • The KEC instance is in the running state.
  • The KEC instance and the scaling group are in the same region and the same availability zone.
  • The KEC instance and the scaling group are both in the same Virtual Private Cloud (VPC).

7. What requirements does a Server Load Balancing (SLB) instance need to meet before it can be attached to a scaling group?

The SLB instance and the scaling group must be in the same VPC.

8. Can Auto Scaling automatically scale up or down the configurations of KEC instances?

No. Auto Scaling cannot scale up or down the configurations of KEC instances. Auto Scaling is a service that automatically scales in or scales out KEC instances based on your business needs and policies. Auto Scaling can automatically add KEC instances when your business load grows, and remove KEC instances when your business load drops. Auto Scaling currently does not support scale-up or scale-down. That is, Auto Scaling cannot automatically adjust the CPU, memory, or bandwidth configurations of KEC instances.

9. Do I have to use Auto Scaling together with SLB and cloud platform monitoring?

Currently, you must use Auto Scaling together with SLB.

10. How do I configure Auto Scaling to scale out a batch of KEC instances during a period of time?

You can create two scheduled tasks for your scaling group and specify the expected number of KEC instances in the scaling group respectively for the two scheduled tasks. In this way, you can use one scheduled task to scale out KEC instances at the start of the time period, and use the other scheduled task to scale in KEC instances at the end of the time period.

11. What removal policies does a scaling group support?

Auto Scaling provides two removal policies:

  • Remove Earliest KEC Instances: Preferentially removes the earliest automatically added KEC instance, and then removes the earliest manually added KEC instance after all automatically added KEC instances are removed.

  • Remove Latest KEC Instances: Preferentially removes the latest automatically added KEC instance, and then removes the latest manually added KEC instance after all automatically added KEC instances are removed.

12. What activities are suspended when a scaling group is disabled?

When a scaling group is disabled, it does not automatically trigger scale activities, but limits on the scaling group still apply.

When a scaling group is disabled, the following activities cannot be triggered:

  • Scheduled task execution
  • Health check

However, to ensure proper business running, Auto Scaling still impose the following limits on the scaling group:

  • If the number of KEC instances in the scaling group is less than the minimum number after you manually remove KEC instances, the KEC instances fail to be removed.

  • If the number of KEC instances in the scaling group is greater than the maximum number after you manually add KEC instances, the KEC instances fail to be added.

  • No scaling activity is triggered when you manually increase the maximum and minimum numbers of KEC instances in the scaling group.

13. What are the rules for removing KEC instances from a scaling group?

  • Removal of manually added KEC instances: The removed KEC instances are no longer managed by the scaling group. However, Auto Scaling does not release the KEC instances or detach them from the SLB instance.

  • Removal of automatically added KEC instances: The removed KEC instances are released and detached from the SLB instance.

14. Does Auto Scaling support projects?

Currently, Auto Scaling does not support projects. You can only attach an SLB instance in the default project to your scaling group.

15. How does Auto Scaling collect metric data to implement alarm-triggered polices?

Assume that Auto Scaling needs to monitor the maximum value of a metric. Auto Scaling collects the value of the specified metric from each KEC instance every 1 minute in each cycle. If the maximum value of the obtained values meets the specified condition in multiple consecutive cycles, Auto Scaling triggers a scaling activity. The number of consecutive cycles can be customized.

On this page
Pure ModeNormal Mode

Pure Mode

Click to preview the document content in full screen
Feedback