All Products
Search
Document Center

Auto Scaling:Cooldown period

Last Updated:Oct 22, 2024

A cooldown period refers to a period of lockdown time after a scaling activity in a scaling group is complete. During the cooldown period, the scaling group does not respond to scaling requests. You can configure a cooldown period to control the scaling frequency. This topic describes the rules and scenarios of the cooldown period feature. This topic also describes how to configure a cooldown period.

Overview of the cooldown period feature

A cooldown period is the minimum interval between two consecutive scaling activities that are triggered by event-triggered tasks. During the cooldown period, new scaling activities that are triggered by event-triggered tasks are rejected.

Important

If you configure a cooldown period, Auto Scaling rejects only the scaling activities that are triggered by event-triggered tasks. Scaling activities that are triggered by other scaling tasks, such as manual execution of scheduled tasks and manual changing of the expected, minimum, or maximum number of instances, can be executed as expected.

  • Classification

    • Default Cooldown Time (Seconds): specifies the default cooldown period of scaling groups.

    • Cooldown Time: specifies the cooldown period of simple scaling rules that are defined in event-triggered tasks. If you do not configure this parameter, the value of the Default Cooldown Time (Seconds) parameter is automatically used.

  • Applicable scope

    The cooldown period feature is applicable to scaling activities that are triggered by event-triggered tasks of the system monitoring type.

  • Calculation rules

    • After a scaling activity is triggered, the cooldown period begins when the last instance is added to or removed from the scaling group. If no instance is added to or removed from the scaling group after a scaling activity is triggered, the cooldown period does not start.

    • You can configure the Default Cooldown Time (Seconds) and Cooldown Time parameters at the same time. In this case, the value of the Cooldown Time parameter takes precedence.

    Important
    • The first scaling activity that is triggered in a scaling group is not affected by the configured cooldown period.

Scenarios

Scenario

Execution

Result

  • The Default Cooldown Time (Seconds) parameter of a scaling group is set to 600.

  • The Cooldown Time parameter of a scale-out rule named add3 is set to 900.

After the add3 rule is executed to trigger a scaling activity, three instances are added to the scaling group.

After the third instance is added to the scaling group, the value of the Cooldown Time parameter takes effect. In this case, new scaling activities that are triggered by event-triggered tasks are not accepted until the 15-minute cooldown period ends.

  • The Default Cooldown Time (Seconds) parameter of a scaling group is set to 600.

  • The Cooldown Time parameter of a scale-in rule named remove1 is not configured.

  1. Phase 1: After a scaling activity is triggered based on the execution of the remove1 rule at 18:00:00, one instance is removed from the scaling group.

  2. Phase 2: The scaling group enters the Disabled state at 18:02:00 and re-enters the Enabled state at 18:05:00.

  1. In Phase 1, scaling activities that are triggered by event-triggered tasks are rejected in the scaling group until 18:10:00.

  2. In Phase 2, scaling activities that are triggered by event-triggered tasks between 18:05:00 and 18:10:00 can be executed as expected.

    Note

    After a scaling activity is complete, Auto Scaling rejects new scaling activities that are triggered by event-triggered tasks during the 600-second cooldown period.

  • The Default Cooldown Time (Seconds) parameter of a scaling group is set to 600.

  • The Cooldown Time parameter of a scale-out rule named add1 is set to 600.

  1. Phase 1: After a scaling activity is triggered based on the execution of the add1 rule at 18:00:00, one instance is added to the scaling group.

  2. Phase 2: You manually execute the add1 rule at 18:05:00.

  1. In Phase 1, scaling activities that are triggered by event-triggered tasks are rejected in the scaling group until 18:10:00.

  2. In Phase 2, the add1 rule can bypass the cooldown period and immediately adds one instance to the scaling group.

Configure a cooldown period

Configure the Default Cooldown Time (Seconds) parameter of a scaling group

Modify the Default Cooldown Time (Seconds) parameter of an existing scaling group

  1. Log on to the Auto Scaling console.

  2. In the left-side navigation pane, click Scaling Groups.

  3. In the top navigation bar, select the region where Auto Scaling is activated.

  4. On the Scaling Groups page, find the scaling group whose Default Cooldown Time (Seconds) parameter you want to modify and click Details in the Actions column to go to the scaling group details page. In the Instance Scaling Overview section, click the image icon to open the Edit Instance Scaling Overview dialog box.

  5. Modify the Default Cooldown Time (Seconds) parameter based on your business requirements.

  6. Click OK.

Configure the Default Cooldown Time (Seconds) parameter when you create a scaling group

When you create a scaling group on the Create by Form tab, you can configure the Default Cooldown Time (Seconds) parameter based on your business requirements, as shown in the following figure.

image

For information about how to create a scaling group, see Create a scaling group of the ECS type or Create a scaling group of the Elastic Container Instance type.

Configure the Cooldown Time parameter of a simple scaling rule

Modify the Cooldown Time parameter of an existing simple scaling rule

  1. Log on to the Auto Scaling console.

  2. In the left-side navigation pane, click Scaling Groups.

  3. In the top navigation bar, select the region where Auto Scaling is activated.

  4. On the Scaling Groups page, find the scaling group whose simple scaling rule you want to manage and click Details in the Actions column to go to the scaling group details page.

  5. Choose Scaling Rules and Event-triggered Tasks > Scaling Rules. Find the scaling rule that you want to manage and click Edit in the Actions column to open the Edit Scaling Rule dialog box.

  6. Modify the Cooldown Time parameter based on your business requirements.

  7. Click OK.

Configure the Cooldown Time parameter when you create a simple scaling rule

When you create a simple scaling rule, you can configure the Cooldown Time parameter based on your business requirements, as shown in the following figure.

image

For more information about how to create a scaling rule, see Manage scaling rules.

References

  • For information about how to modify the default cooldown period of a scaling group by calling an API operation, see ModifyScalingGroup.

  • For information about how to modify the cooldown period of a simple scaling rule by calling an API operation, see ModifyScalingRule.