This document explains how to resolve resource availability errors that might occur when you try to request new Compute Engine resources or create reservations of Compute Engine resources. Resource errors occur when you try to request resources in a zone that can't accommodate your request due to the current unavailability of a Compute Engine resource, such as GPUs or vCPUs.
Resource errors aren't related to your Compute Engine quota. These errors only apply to the resources that you specified in your request when you sent it; they don't apply to all resources in a zone.
Common error messages
The following are examples of common resource errors that you might encounter when you request new Compute Engine resources or create new reservations:
ZONE_RESOURCE_POOL_EXHAUSTED
ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS
The zone 'projects/PROJECT_ID/zones/ZONE' does not have enough resources available to fulfill the request. Try a different zone, or try again later.
A VM_TYPE_AND_SIZE VM instance with RESOURCE_ATTACHMENT is currently unavailable in the ZONE zone. Capacity changes frequently, so try your request in a different zone, with a different VM hardware configuration, or at a later time. For more options, see troubleshooting documentation.
A VM_TYPE_AND_SIZE VM instance with RESOURCE_ATTACHMENT is currently unavailable in the ZONE zone, because of REASON. Consider trying your request in the ZONE zone(s), which currently has capacity to accommodate your request. If you cannot move your VM to ZONE, review the REASON failure resolution instructions available in troubleshooting documentation, then try your request again. If your workload can't accommodate the suggested resolution, try your request with a different VM hardware configuration or at a later time.
Some error messages include a reason field that details which specific
resources Compute Engine couldn't provide. For more information, see the
Resource error reasons and recommendations in this
document.
How to resolve resource errors
If the error message that you encountered includes a reason field, then, to
see specific guidance to resolve the error, see
Resource error reasons and recommendations in this
document. Otherwise, the best approach for resolving a resource availability
error involves trying one or more of the following. The following approaches are
ordered from the least to the most disruptive for your workload.
Retry your request at a different time. Resource availability can be transient, and you can resolve this error by requesting resources at a later time.
Retry your request in a different region or zone. Try requesting resources in a different region or zone.
Use a different machine configuration. You can change one or more of the following properties when you request resources:
Request a smaller number of compute instances.
Request a different machine series or machine type.
Request a different number of Local SSD disks or GPUs.
Use a different provisioning model. If you can't create standard compute instances, then try creating Flex-start VMs or Spot VMs. Different provisioning models have different capacity pools and availability characteristics. For more information, see Compute Engine instances provisioning models.
Additionally, if you're trying to create a regional managed instance group
(MIG), try changing the distribution shape of the MIG to ANY,
ANY_SINGLE_ZONE, or BALANCED. For more information, see
Regional MIG target distribution shape.
Resource error reasons and recommendations
The following table provides information about the reason field present in
some resource error messages, as well as recommendations about resolution
strategies for each reason.
Error reason |
Description | Recommendation |
|---|---|---|
resource_availability |
The type and size of compute instance that you requested is currently unavailable in the zone that you requested it in. | Try one of the following:
|
cpu_availability |
A compute instance with the amount of CPU that you requested is currently unavailable in the zone that you requested it in. | Try one of the following:
|
memory_availability |
A compute instance with the amount of memory that you requested is currently unavailable in the zone that you requested it in. | Try one of the following:
|
local_ssd_availability |
A compute instance with the amount of local SSD that you requested is currently unavailable in the zone that you requested it in. | Try one of the following:
|
gpu_availability |
A compute instance with the GPU that you requested is currently unavailable in the zone you requested it in. | Try requesting the compute instance in another zone. |
configuration_availability |
A compute instance with the configuration that you requested isn't supported in the zone that you requested it in. | Retry your request in a zone that supports the machine type and configuration you require. To learn more about which machine types are supported in each region and zone, see Available regions and zones. To learn more about the configurations that each machine type supports, see Machine series comparison. |
If you're unable to resolve the error by using any of the preceding resolution recommendations, then contact support.