Autoscaling automatically adds VMs (scales out) or removes VMs (scales in) your managed instance group (MIG). This document explains how an autoscaler determines when to scale your MIGs.
How autoscalers calculate recommended size and affect target size
When you configure an autoscaler for a MIG, the autoscaler constantly monitors the group and sets the group's recommended size to the number of virtual machine (VM) instances that are required in order to serve peak load over the last 10 minutes. These last 10 minutes are referred to as the stabilization period.
The recommended size is constrained by the minimum and maximum number of instances that you set in the autoscaling policy.
If your autoscaling policy includes scale-in controls, then the recommended size is further constrained by your scale-in controls.
If you enable predictive autoscaling, then the autoscaler uses historical CPU utilization patterns to forecast future load, and it sets the group's recommended size based on its prediction.
The MIG's response to the autoscaler's recommended size depends on how you
configure the autoscaler's
ON. The MIG sets its target size to the recommended size, and then Compute Engine automatically scales out the MIG to meet its target size.
ONLY_SCALE_OUT. The MIG's target size can only be increased in response to an increased recommended size.
OFF. The target size is unaffected by the recommended size. However, the recommended size is still calculated.
If the autoscaler configuration is deleted, then no recommended size is calculated.
Gaps between target and actual utilization metrics
When using metrics-based autoscaling policies, you might notice that, for smaller instance groups, the actual utilization of the instance group and the target utilization might seem far apart. This is because an autoscaler always acts conservatively by rounding up or down when it interprets utilization data and determines how many instances to add or remove. This prevents the autoscaler from adding an insufficient number of resources or removing too many resources.
For example, if you set a utilization target of 0.7 and your application exceeds the utilization target, the autoscaler might determine that adding 1.5 virtual machine (VM) instances would decrease the utilization to close to 0.7. Because you cannot add 1.5 VM instances, the autoscaler rounds up and adds two instances. This might decrease the average CPU utilization to a value below 0.7 but ensures that your app has enough resources to support it.
Similarly, if the autoscaler determines that removing 1.5 VM instances would increase your utilization too close to 0.7, it will remove just one instance.
For larger groups with more VM instances, the utilization is divided up over a larger number of instances, and adding or removing VM instances causes less of a gap between actual utilization and target utilization.
If you use schedule-based autoscaling with metrics-based policies, an active schedule might require more VMs than your utilization needs. In these situations, your actual utilization is lower than your target utilization because the autoscaling schedule determines the recommended size of the instance group.
Regional MIGs and uneven VM distributions
If a region has an unbalanced number of instances between zones, whether due to recovering from a zonal failure or due to an unevenly distributed workload, autoscaling keeps more instances running in zones that have a higher than average actual utilization. Compute Engine takes this precaution to guarantee high availability across the region as a whole as well as all zones individually, even if some of the zones experience heavier load than others.
Delays in scaling out
When you configure autoscaling, you specify a cool down period that reflects the length of time it takes for your VMs to initialize. The autoscaler ignores usage data from VMs during that cool down period.
If you set a cool down period value that is significantly longer than the time it takes for an instance to initialize, then your autoscaler might ignore legitimate utilization data, and it might underestimate the required size of your group.
Delays in scaling in
For the purposes of scaling in, the autoscaler calculates the group's recommended target size based on peak load over the last 10 minutes. These last 10 minutes are referred to as the stabilization period.
Observing the last 10 minutes of usage helps the autoscaler:
- Ensure that usage information collected from the instance group is stable.
- Prevent behavior where an autoscaler continuously adds or removes instances at an excessive rate.
- Safely remove instances by determining that the smaller group size is enough to support peak load from the last 10 minutes.
This 10 minute stabilization period might appear as a delay in scaling in, but it is actually a built-in feature of autoscaling. The delay also ensures that if a new instance is added to the managed instance group, the instance is running for at least 10 minutes before it is eligible to be scaled in.
Cool down periods for new instances are ignored when deciding whether to scale in a group.
Connection draining causing delays
If the group is part of a backend service that has enabled connection draining, it can take up to an additional 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted.
When you configure autoscaler scale-in controls, you control the speed of scaling in. The autoscaler never scales in faster than your configured rate:
- When load declines, the autoscaler maintains the size for the group at a level required to serve the peak load observed in the last 10 minutes (stabilization period). This works the same with and without scale-in controls.
- An autoscaler without scale-in controls keeps only enough instances required to handle recently observed load. After the stabilization period, the autoscaler removes all unneeded instances in one step. With a sudden drop in load this can lead to a dramatic reduction of instance group size.
- An autoscaler with scale-in controls limits how many VM instances can be removed in a configured period of time (here 10 VMs in 20 minutes). This slows down the instance reduction rate.
- With a new load spike, the autoscaler adds new instances to handle the load. However, due to a long initialization time, the new VMs are not ready to serve the load. With scale-in controls, the previous capacity was kept, allowing existing VMs to serve the spike.
You control the scale-in rate by configuring the Autoscaler's maximum allowed reduction within a trailing time window, specifically:
- Maximum allowed reduction (
maxScaledInReplicas: number or % of VM instances). The number of instances that your workload can afford to lose (from the group's peak size) within the specified trailing time window. Use this parameter to constrain how much your group can be scaled in so that you can still serve a likely load spike until more instances start serving. The lower the maximum allowed reduction, the slower the rate of scale in.
- Trailing time window (
timeWindowSec: seconds). Time during which a load spike is likely to follow a temporary decline and during which you don't want your group size to scale in beyond the maximum allowed reduction. Use this parameter to define the time window in which autoscaler will look for the peak size sufficient to serve historical load. Autoscaler will not resize below the maximum allowed reduction subtracted from the peak size observed in the trailing time window. With a longer trailing time window, the autoscaler considers more historical peak load, which makes scaling in more conservative and stable.
When you set scale-in controls, the autoscaler constrains scale-in operations to the maximum allowed reduction from the peak size observed in the trailing time window. The autoscaler uses the following steps:
- Continuously monitors the historical peak size observed in the trailing time window.
- Uses the maximum allowed reduction to calculate the
constrained scale-in size (peak size:
- Sets the group's recommended size to the constrained scale-in size. For example, if an autoscaler would resize an instance group to 20 VMs but scale-in constraints only allow a scale in to 40 VMs, then the recommended size is set to 40 VMs.
With scale-in controls, the autoscaler continuously monitors the peak size of an instance group within the configured trailing time window to identify the sufficient size to serve historical load. The autoscaler does not scale in beyond the maximum allowed reduction measured from the observed peak size:
For example, in the diagram above, scale-in controls are configured for a 20 VM maximum allowed reduction in a 30-minute trailing time window:
- When load goes down autoscaler removes 20 VMs, which is the maximum allowed reduction configured in scale-in controls.
- As the load goes up and down, the autoscaler constantly monitors the last 30 minutes trailing time window for the peak size sufficient to serve historical load. This peak size is used as a base for scale-in controls to limit scale-in rate. If, in the last 30 minutes, peak size was 70 VMs and the maximum allowed reduction is set to 20 VMs, the autoscaler can scale in to 50 VMs. If the current size is 65 VMs, the autoscaler can remove only 15 VMs.
- As load decreases, the autoscaler continues to remove VM instances but limits the rate to at most 20 VMs from the peak instance group size measured in the last 30 minutes.
The maximum allowed reduction in group size might happen all at once, so you should configure the maximum allowed reduction so that your application can afford losing that many instances at once. Use the maximum allowed reduction parameter to indicate how much reduction in serving capacity your application can tolerate.
By limiting the number of VM instances that autoscaling can remove and by increasing the observed trailing time window, applications with load spikes and long initialization times should experience improved availability. In particular, the instance group size doesn't drop abruptly in response to a significant drop in load and instead decreases gradually over time. If load spikes soon after a scale in has occurred, the remaining number of VMs should still be able to absorb the spike within your tolerance. In addition, fewer VMs must be started in order to sufficiently serve the spike.
You can configure scale-in controls for autoscaling of both zonal and regional MIGs. The configuration is the same for both cases. Scale-in controls work for any group size.
Scale-in controls versus autoscaler stabilization
Configuring scale-in controls does not mean switching off the autoscaler's built-in stabilization mechanism. The autoscaler always maintains the instance group size at a level required to serve peak load, observed during the stabilization period of the trailing 10 minutes. Scale-in controls give you an additional mechanism to control the rate at which an instance group is resized.
Trailing time window
|Configurable?||No, non-configurable||Yes, configurable|
|What is monitored?||Monitors peak load over the previous 10 minutes||Monitors peak size of the instance group in the previous period set by trailing time window|
|How does this help?||Ensures that the instance group size remains sufficient to serve the peak load that was observed during the last 10 minutes.||Ensures that the instance group size is not reduced by more VM instances than your workload can tolerate when handling load spikes over a specified time window.|
Scale-in controls with autoscaler mode
There are two similar yet slightly different scenarios when your MIG is not autoscaled and you want to turn on autoscaling. These depend on whether you are configuring autoscaling for the first time or whether autoscaling is configured but temporarily restricted or off.
Configuring autoscaler for the first time
When you have a non-autoscaled MIG and you configure autoscaling from scratch, the autoscaler uses the current MIG size as a starting point. Before scaling in, the autoscaler uses the stabilization period and then it uses scale-in controls to constrain the scale-in rate:
Changing autoscaler mode
With autoscaling mode, you can temporarily turn off or restrict autoscaling activities. The autoscaler's configuration persists and the autoscaler continues to perform background calculations while the autoscaler is off or restricted. The autoscaler takes into account scale-in controls in its background calculations while in off or restricted mode. All autoscaling activities resume using the most recent calculations when you turn autoscaling on again or when you lift the restriction:
- Autoscaler turned ON behaves as usual (with scale-in controls in this case).
- When you turn autoscaler OFF, it still calculates the recommended instance group size based on load. Autoscaler calculations still consider scale-in controls. However, the autoscaler does not apply size calculations when autoscaler is OFF. The instance group size stays constant until autoscaler is ON again.
- When you turn the autoscaler ON again it immediately applies the previously calculated size. This allows faster scaling to the correct size. Re-enabling the autoscaler can cause an abrupt scale in (here from 80 to 40 VM instances). This is safe because background calculations already consider scale-in controls.
Preparing to stop instances
When the autoscaler scales in, it determines the number of VM instances it needs to shut down, and selects VM instances that have low utilization to remove from the instance group. Before an instance is stopped, you might want to make sure these instances perform certain tasks, such as closing any existing connections, gracefully shut down any apps or app servers, uploading logs, and so on. You can instruct your instance to perform these tasks using a shutdown script.
A shutdown script runs, on a best-effort basis, in the brief period between when the stopping request is made and when the instance is actually stopped. During this period, Compute Engine attempts to run your shutdown script to perform any tasks you provide in the script.
This is particularly useful if you are using load balancing with your managed instance group. If your instance becomes unhealthy, it might take some time for the load balancer to recognize that the instance is unhealthy, causing the load balancer to continue sending new requests to the instance. With a shutdown script, the instance can report that it is unhealthy while it is shutting down so that the load balancer can stop sending traffic to the instance. For more information about load balancing health checks, see the health checks overview.
For more information about shutdown scripts, see Shutdown scripts.
Viewing autoscaling charts for utilization
If you have a managed instance group that is being autoscaled, Compute Engine provides an autoscaling chart that tracks the total utilization and the number of autoscaled instances at any point in time. You can access this chart in the Google Cloud Console.
- In the Cloud Console, go to the Instance groups page.
- Click the name of an autoscaled managed instance group you want to view. The group must be using autoscaling based on CPU utilization (other autoscaling metrics are not yet supported).
On the managed instance group details page, select the Monitoring tab, if it is not already selected.
Make sure that Autoscaled size is selected in the drop-down list.
The charts track the number of instances over CPU usage. Use the following information to understand these charts.
- The blue line on the upper graph indicates the number of instances in the managed instance group.
- The blue line on the lower chart shows the total CPU utilization of the group.
- The green line on the lower chart shows the remaining available capacity
of the managed instance group.
- If the green line is above the blue line, there is a large amount of capacity available and your VM instances are likely under utilized.
- If the green line is below the blue line, then there is little, if any, remaining capacity and you should add more instances to the instance group.
- If your capacity drops, then it likely means that the size of your instance group has decreased, so the blue line on the upper chart will also drop. Similarly, if your capacity increases, the size of your instance group has likely also increased.
For example, the following graph captures an autoscaled managed instance group that reaches capacity, which causes the autoscaler to add more VM instances to the group, increasing capacity of the group.
Viewing status messages
When the autoscaler experiences an issue scaling, it returns a warning or error message. You can review these status messages in one of two ways.
View status messages on the Instance groups page
You can view status messages directly on the Instance groups page in the Google Cloud Console .
- In the Google Cloud Console, go to the Instance groups page.
Look for any instance groups that have the Caution icon (!). For example:
Hover over a status icon to get details of the status message.
View status messages on the Instance group details page
You can go directly to the details page of a specific instance group to view relevant status messages.
- In the Cloud Console, go to the Instance groups page.
- Click the instance group for which you want to view status messages.
On the details page, view the status message on the Members tab. For example:
Commonly returned status messages
When the autoscaler experiences an issue scaling, it returns a warning or error message. Here are some commonly returned messages and what they mean.
All instances in the instance group are unhealthy (not in RUNNING state). If this is an error, check the instances.
- All of the instances in the instance group have a state that is something
RUNNING. If this is intentional, then you can ignore this message. If this is not intentional, troubleshoot the instance group.
The number of instances has reached the maxNumReplicas. The autoscaler cannot add more instances.
- When you created the autoscaler, you indicated the maximum number of
instances the instance group can have. The autoscaler is currently attempting
to scale out the instance group to meet demand but has reached the
maxNumReplicas. For information about how to update
maxNumReplicasto a larger number, see Updating an autoscaler.
The monitoring metric that was specified does not exist or does not have the required labels. Check the metric.
- You are autoscaling using a Cloud Monitoring metric but the metric you provided does not exist or lacks the necessary labels. Depending on whether the metric is a standard or custom metric, different labels are required. See the documentation for Scaling based on a Monitoring metric for more information.
Quota for some resources is exceeded. Increase the quota or delete resources to free up more quota.
- You can get information about your available quota on the Quota page in the Google Cloud Console.
Autoscaling does not work with an HTTP/S load balancer configured for maxRate.
- The instance group is being load balanced using the
maxRateconfiguration but the autoscaler does not support this mode. Either change the configuration or disable autoscaling. To learn more about
maxRate, read the Restrictions and guidelines in the load balancing documentation.
The autoscaler is configured to scale based on a load balancing signal but the instance group has not received any queries from the load balancer. Check that the load balancing configuration is working.
- The instance group is being load balanced but the group has no incoming queries. The service might be experiencing a period of idleness, in which case there is nothing to worry about. However, this message can also be caused by misconfiguration; for example an autoscaled instance group might be the target of more than one load balancer, which is not supported. For a full list of guidelines, see Restrictions and guidelines in the load balancing documentation.