View, cancel, or delete resize requests in a MIG

Preview — Resize requests in regional MIGs

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

This document describes how to do the following aftercreating a resize requestin a managed instance group (MIG):

After youcreate resize requestsin a MIG, you can do one or more of the following:

  • View resize requests to monitor their states or troubleshoot them.

  • Cancel resize requests to stop the MIG from creating the requested number ofvirtual machine (VM) instances.

  • Delete resize requests when you no longer need them.

Before you begin

Required roles

To get the permissions that you need to view, cancel, or delete resize requests in a MIG, ask your administrator to grant you theCompute Instance Admin (v1) (roles/compute.instanceAdmin.v1) IAM role on the project. For more information about granting roles, seeManage access to projects, folders, and organizations.

This predefined role contains the permissions required to view, cancel, or delete resize requests in a MIG. To see the exact permissions that are required, expand theRequired permissions section:

Required permissions

The following permissions are required to view, cancel, or delete resize requests in a MIG:

  • To cancel or delete resize requests in a MIG: compute.instanceGroupManagers.update
  • To view a list of resize requests in a MIG: compute.instanceGroupManagers.list
  • To view the details of a resize request: compute.instanceGroupManagers.get

You might also be able to get these permissions withcustom roles or otherpredefined roles.

View your resize requests

To view information about the resize requests in a MIG, use one of the followingmethods:

View a list of resize requests in a MIG

To view a list of all resize requests in a MIG, select one of the followingoptions:

To view a list of all resize requests in a regional MIG, use thegcloud CLI or REST API. Otherwise, to view a list of allresize requests in a zonal MIG, select any of the following options:

Console

  1. In the Google Cloud console, go to theInstance groups page.

    Go to Instance groups

  2. In theName column, click the name of the MIG that contains resizerequests.

    The overview page of the MIG opens.

  3. In theResize requests row, clickEdit resize requests.

    TheResize requests pane appears. If a resize request'sDetails column shows theQuota exceeded orETA: indefinitevalue, then your request has encountered an error. You can click thesevalues to learn more.

    For more information about troubleshooting errors, seeView the details of a resize request in thisdocument.

gcloud

Replace the following:

  • INSTANCE_GROUP_NAME: the name of aMIG with accepted, successful, canceled, or failed resize requests.

  • ZONE: the zone where the MIG is located.

  • REGION: the region where the MIG is located.

The output is similar to the following for a zonal MIG:

NAME: rr-01LOCATION: us-central1-aSCOPE: zoneRESIZE_BY: 5STATE: SUCCEEDEDREQUESTED_RUN_DURATION: P1DNAME: rr-02LOCATION: us-central1-aSCOPE: zoneRESIZE_BY: 10STATE: ACCEPTEDREQUESTED_RUN_DURATION: P3D

REST

  • To view a list of resize requests in a zonal MIG, send aGET requestusing theinstanceGroupManagerResizeRequests.list method.

    GET https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME/resizeRequests

  • To view a list of resize requests in a regional MIG, send aGET requestusing thebeta.regionInstanceGroupManagerResizeRequests.list method.

    GET https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/regionInstanceGroupManagers/INSTANCE_GROUP_NAME/resizeRequests

Replace the following:

  • PROJECT_ID: the ID of the project where a MIG withaccepted, successful, canceled, or failed resize requests is located.

  • ZONE: the zone where the MIG is located.

  • REGION: the region where the MIG is located.

  • INSTANCE_GROUP_NAME: the name of an existingMIG with accepted, successful, canceled, or failed resize requests.

The output from a zonal MIG is similar to the following:

{  "kind": "compute#instanceGroupManagerResizeRequestList",  "id": "projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests",  "items": [    {      "kind": "compute#instanceGroupManagerResizeRequest",      "id": "4247139565532196982",      "creationTimestamp": "2024-01-08T07:51:53.034-08:00",      "name": "rr-01",      "zone": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a",      "count": 5,      "resizeBy": 5,      "requestedRunDuration": {        "seconds": "86400",        "nanos": 0      },      "state": "SUCCEEDED",      "status": {},      "selfLink": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests/rr-01",      "selfLinkWithId": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests/4247139565532196982"    },    {      "kind": "compute#instanceGroupManagerResizeRequest",      "id": "8095866098849525652",      "creationTimestamp": "2024-01-11T08:04:11.851-08:00",      "name": "rr-02",      "zone": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a",      "count": 10,      "resizeBy": 10,      "requestedRunDuration": {        "seconds": "259200",        "nanos": 0      },      "state": "ACCEPTED",      "status": {},      "selfLink": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests/rr-02",      "selfLinkWithId": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests/8095866098849525652"    }  ],  "selfLink": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests"}

View the details of a resize request

You can view the details of a resize request to review its configuration and,optionally, troubleshoot it if the request hasn't succeeded yet.

If an accepted resize request isn't succeeding, then you can troubleshoot it bychecking thestatus.lastAttempt.error.errors.code field in the request'sdetails. The possible error codes are as follows:

  • QUOTA_EXCEEDED: your project lacks quota for the requested resources.To increase your project's quota, seeRequest a quota adjustment.

  • ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS: the requested resources aretemporarily unavailable. Compute Engine has scheduled the creationof the requested resources and plans to create them when they becomeavailable. If themessage field containsExpected time is indefinite,then Google recommends canceling the request and trying one or more of thefollowing:

    • Create a new resize request with a lower number of requested VMs.

    • Use a different machine type in the MIG, and then create a new resizerequest. To use a different machine type,create a new instance template,and then use that template tocreate or update a MIG.

    • Create a resize request in a MIG located in a different region or zone.

To view the details of a resize request, select one of the following options:

gcloud

Replace the following:

  • INSTANCE_GROUP_NAME: the name of aMIG.

  • RESIZE_REQUEST_NAME: the name of a resizerequest that you want to view the details of.

  • ZONE: the zone where the MIG is located.

  • REGION: the region where the MIG is located.

The output is similar to the following for a zonal MIG:

creationTimestamp: '2024-09-23T02:27:09.575-07:00'id: '6386622402379156098'kind: compute#instanceGroupManagerResizeRequestname: example-requestrequestedRunDuration:  nanos: 0  seconds: '86400'resizeBy: 10selfLink: https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests/example-requestselfLinkWithId: https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests/6386622402379156098state: ACCEPTEDstatus:  lastAttempt:    error:      errors:      - code: QUOTA_EXCEEDED        message: Quota 'NVIDIA_A100_GPUS' exceeded. Limit: 1500 in region us-central1.      - code: ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS        message: There are currently not enough resources available to fulfill the request. Expected time is indefinite.        - errorDetails:          - errorInfo:            - metadatas:              - estimatedAvailabilityTime: '9999-12-31T23:59:59.999999999Z'zone: https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a

REST

  • To view the details of a resize request in a zonal MIG, send aGETrequest using theinstanceGroupManagerResizeRequests.get method.

    GET https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME/resizeRequests/RESIZE_REQUEST_NAME

  • To view the details of a resize request in a regional MIG, send aGETrequest using thebeta.regionInstanceGroupManagerResizeRequests.get method.

    GET https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/regionInstanceGroupManagers/INSTANCE_GROUP_NAME/resizeRequests/RESIZE_REQUEST_NAME

Replace the following:

  • PROJECT_ID: the ID of the project where the zonalMIG is located.

  • ZONE: the zone where the MIG is located.

  • REGION: the region where the MIG is located.

  • INSTANCE_GROUP_NAME: the name of a MIG where theresize request is located.

  • RESIZE_REQUEST_NAME: the name of an existing resizerequest that you want to view the details of.

The output is similar to the following:

{  "kind": "compute#instanceGroupManagerResizeRequest",  "id": "6386622402379156098",  "creationTimestamp": "2024-09-23T02:27:09.575-07:00",  "name": "example-request",  "zone": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a",  "resizeBy": 10,  "requestedRunDuration": {    "seconds": "86400",    "nanos": 0  },  "state": "SUCCEEDED",  "status": {    "lastAttempt": {      "error": {        "errors": [          {            "code": "QUOTA_EXCEEDED",            "message": "Quota 'NVIDIA_A100_GPUS' exceeded. Limit: 1500 in region us-central1."          },          {            "code": "ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS",            "message": "There are currently not enough resources available to fulfill the request. Expected time is indefinite.",            "errorDetails": [              {                "errorInfo":{                  "metadatas":{                    "estimatedAvailabilityTime": "9999-12-31T23:59:59.999999999Z"                  }                }              }            ]          }        ]      }    }  },  "selfLink": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests/example-request",  "selfLinkWithId": "https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-a/instanceGroupManagers/example-mig/resizeRequests/6386622402379156098"}

Cancel resize requests in a MIG

You can cancel resize requests in a MIG to stop the MIG from attempting tocreate the requested number of VMs. You can cancel accepted (ACCEPTED) resizerequests only. After canceling a resize request, you can eitherdelete it or let Compute Engine automatically deleteit after 14 days.

To cancel multiple resize requests simultaneously, use theGoogle Cloud console or Google Cloud CLI. Otherwise, to cancel a single resizerequest, select any of the following options:

Console

  1. In the Google Cloud console, go to theInstance groups page.

    Go to Instance groups

  2. In theName column, click the name of the MIG that contains resizerequests.

    The overview page of the MIG opens.

  3. In theResize requests row, clickEdit resize requests.

    TheResize requests pane appears.

  4. Select the resize requests to cancel.

  5. ClickCancel, and thenclickConfirm.

gcloud

Replace the following:

  • INSTANCE_GROUP_NAME: the name of aMIG with accepted resize requests.

  • RESIZE_REQUEST_NAMES: a comma-separated list of namesof accepted resize requests in the specified zonal MIG. For example,specifyrequest-1,request-2.

  • ZONE: the zone where the MIG is located.

  • REGION: the region where the MIG is located.

REST

  • To cancel a resize request in a zonal MIG, send aPOST request using theinstanceGroupManagerResizeRequests.cancel method.

    POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME/resizeRequests/RESIZE_REQUEST_NAME/cancel

  • To cancel a resize request in a regional MIG, send aPOST request usingthebeta.regionInstanceGroupManagerResizeRequests.cancel method.

    POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/regionInstanceGroupManagers/INSTANCE_GROUP_NAME/resizeRequests/RESIZE_REQUEST_NAME/cancel

Replace the following:

  • PROJECT_ID: the ID of the project where an existingzonal MIG with an accepted resize request is located.

  • ZONE: the zone where the MIG is located.

  • REGION: the region where the MIG is located.

  • INSTANCE_GROUP_NAME: the name of the MIG.

  • RESIZE_REQUEST_NAME: the name of the resize requestto cancel.

Delete resize requests in a MIG

By default, Compute Engine automatically deletes a resize request 14days after setting the request's state to one of the following:

  • Successful (SUCCEEDED)

  • Failed (FAILED)

  • Canceled (CANCELLED)

However, you can immediately delete a resize request before then, as describedin this section.

Deleting a successful resize request doesn't delete the VMs created through therequest. The MIG automatically deletes those VMs at the end of their requestedrun duration. However, if your job has finished running and you no longer needthe VMs, thendelete the VMs.

To delete multiple resize requests simultaneously, use theGoogle Cloud console or gcloud CLI. Otherwise, to delete a singleresize request, select any of the following options:

Console

  1. In the Google Cloud console, go to theInstance groups page.

    Go to Instance groups

  2. In theName column, click the name of the MIG that contains resizerequests.

    The overview page of the MIG opens.

  3. In theResize requests row, clickEdit resize requests.

    TheResize requests pane appears.

  4. Select the resize requests to delete.

  5. ClickDelete, and thenclickConfirm.

gcloud

Replace the following:

  • INSTANCE_GROUP_NAME: the name of aMIG with successful, failed, or canceled resize requests.

  • RESIZE_REQUEST_NAMES: a comma-separated list of namesof resize requests to delete in the MIG. For example, specifyrequest-1,request-2.

  • ZONE: the zone where the MIG is located.

  • REGION: the region where the MIG is located.

REST

  • To delete a resize request in a zonal MIG, send aDELETE request using theinstanceGroupManagerResizeRequests.delete method.

    DELETE https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME/resizeRequests/RESIZE_REQUEST_NAME

  • To delete a resize request in a regional MIG, send aDELETE requestusing thebeta.regionInstanceGroupManagerResizeRequests.delete method.

    DELETE https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/regionInstanceGroupManagers/INSTANCE_GROUP_NAME/resizeRequests/RESIZE_REQUEST_NAME

Replace the following:

  • PROJECT_ID: the ID of the project where an existingzonal MIG with successful, failed, or canceled resize requests islocated.

  • ZONE: the zone where the MIG is located.

  • REGION: the region where the MIG is located.

  • INSTANCE_GROUP_NAME: the name of the MIG.

  • RESIZE_REQUEST_NAME: the name of the resize requestto delete.

What's next

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-15 UTC.