METHOD_NAME: 서비스 메서드 또는 작업의 이름입니다. API 호출의 경우 이 이름은 API 메서드 이름이어야 합니다.
LOCATION: 리소스 위치입니다. 리전, 영역 또는 전역일 수 있습니다. 예를 들어 currentLocations: "us-central1"(리전) 또는 currentLocations: "us-central1-a" 항목은 리전이 "us-central1" 또는 currentLocations: "global"임을 나타냅니다.
오류 로그에서 연결된 methodName 값을 식별합니다. 이 이름은 비율 제한이 초과된 API 메서드를 나타냅니다(예: v1.compute.instances.stop).
감사 로그에서 관련 위치를 파악합니다.
Concurrent operations per project 할당량 및 한도를 확인합니다.
할당량 페이지에는 프로젝트의 할당량 사용량과 한도가 나와 있습니다.
기본적으로 목록은 가장 많이 사용된 할당량이 먼저 표시되도록 정렬되므로 초과될 위험이 있는 한도를 확인하는 데 유용합니다.
목록을 필터링하고 특정 할당량의 사용량과 한도를 보려면 필터 필드에서 할당량 또는 측정항목을 선택합니다.
예를 들어 Concurrent global operations per project operation type 이름으로 할당량을 선택하거나 Service: Compute Engine API, type: System Limit, 키워드 concurrent를 선택하여 모든 동시 작업 할당량을 표시합니다. 필터링하면 동시 할당량 목록이 제공됩니다. 이 목록에서 영향을 받는 할당량을 검색할 수 있습니다.
특정 작업의 할당량을 필터링하려면 측정기준을 필터 쿼리에 추가하고 operation_type(감사 로그에서는 methodName으로 표시됨)을 선택합니다.
예를 들어 instances.stop 작업의 할당량 사용량과 한도를 확인하려면 instances_stop을 선택합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThis document guides you through troubleshooting \u003ccode\u003erateLimitExceeded\u003c/code\u003e errors in Compute Engine, which indicate concurrent operation limit issues.\u003c/p\u003e\n"],["\u003cp\u003eTo find the cause, use the Logs Explorer to filter Compute Engine API error logs using a specific query that looks for \u003ccode\u003erateLimitExceeded\u003c/code\u003e messages, service names, and error codes.\u003c/p\u003e\n"],["\u003cp\u003eThe error logs provide details like the \u003ccode\u003emethodName\u003c/code\u003e of the affected API call and the \u003ccode\u003eLOCATION\u003c/code\u003e of the resource, which can then be used to determine the specific quota being exceeded.\u003c/p\u003e\n"],["\u003cp\u003eThe Quotas page in the Google Cloud console, or the gcloud CLI, can be used to check concurrent operation quotas per project, per project per operation type, or by specific regions to see if current usage is nearing or exceeding set limits.\u003c/p\u003e\n"],["\u003cp\u003eTo avoid future \u003ccode\u003erateLimitExceeded\u003c/code\u003e errors, best practices include waiting for operations to complete, relying on error codes, minimizing retries, using client-side rate limiters, and splitting applications across multiple projects.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot Compute Engine concurrent operations quota\n\n*** ** * ** ***\n\nThis document describes how to troubleshoot concurrent operation limits in Compute Engine that are caused by [`rateLimitExceeded`](https://cloud.google.com/compute/operations-quota) errors.\n\nTo help identify the cause of a `rateLimitExceeded` error, use the following troubleshooting steps:\n\n1. In the Google Cloud console, go to the **Logs Explorer** page:\n\n [Go to **Logs Explorer**](https://console.cloud.google.com/logs/query)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Logging**.\n2. To filter the error logs generated by Compute Engine API, enter the following logging query in the query editor.\n\n ```\n log_id(\"cloudaudit.googleapis.com/activity\")\n protoPayload.serviceName=\"compute.googleapis.com\"\n protoPayload.response.error.code=403\n protoPayload.status.message=\"Rate Limit Exceeded\"\n ```\n\n The filtered error logs should look similar to the following: \n\n ```\n \"protoPayload\":{\n \"@type\": \"type.googleapis.com/google.cloud.audit.AuditLog\",\n \"status\": {\n \"message\": \"Rate Limit Exceeded\"\n }\n \"serviceName\": \"compute.googleapis.com\",\n \"methodName\": \"METHOD_NAME\",\n ...\n ...\n \"response\": {\n \"error\": {\n \"message\": \"Rate Limit Exceeded\",\n \"code\": 403,\n \"errors\": [\n {\n \"message\": \"Rate Limit Exceeded\",\n \"reason\": \"rateLimitExceeded\",\n \"domain\": \"usageLimits\"\n }\n ]\n },\n \"@type\": \"type.googleapis.com/error\"\n },\n \"resourceLocation\": {\n \"currentLocations\": [\n \"LOCATION\"\n ]\n },\n ...\n ... \n ```\n\n The error details contain the following values:\n - \u003cvar translate=\"no\"\u003eMETHOD_NAME\u003c/var\u003e: The name of the service method or operation. For API calls, this name should be the name of the API method.\n\n - \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: The location of the resource. This can be a region, zone or global. For example, the entries `currentLocations: \"us-central1\"`(Regional) or `currentLocations: \"us-central1-a\"` indicate that the region is `\"us-central1\"` or `currentLocations: \"global\"`.\n\n3. Identify the associated `methodName` value from the error log. This name represents the API method for which the rate limit exceeded, for example: `v1.compute.instances.stop`.\n\n4. Identify the relevant location in the audit logs.\n\n5. Check the `Concurrent operations per project` quotas and limits.\n\n ### Console\n\n 1. In the Google Cloud console, go to the **Quotas** page.\n\n [Go to Quotas](https://console.cloud.google.com/iam-admin/quotas)\n\n The **Quotas** page lists the quota usage and limits for your project.\n By default, the list is sorted to show your most used quotas first,\n which helps you see limits that are at risk of being exceeded.\n 2. To filter the list and to view the usage and limit for any specific quota,\n select **Quota** or **Metric** in the **Filter** field.\n\n For example, either select the Quota by the name `Concurrent global operations per project operation type` or\n select `Service: Compute Engine API`, `type: System Limit` and a key word `concurrent` to list all the concurrent operation quotas. Filtering provides a list of concurrent quotas. From this list, you can search for the affected quota.\n To filter the quota for a specific operation, add **Dimensions** to the filter query\n and select the **operation_type** (shown as **methodName** in the audit logs).\n\n For example, select `instances_stop`\n to see the quota usage and limit for the operation `instances.stop`.\n\n To filter the quota for a specific region, add **Dimensions** to the filter query\n and select the **region** (shown as **currentLocations** in the audit logs).\n\n For example, select `us-central1` to see the quota usage and limit for `us-central1` region.\n\n Filters **region** and **operation_type** can be used together to view the quota usage and limit for a specific operation in a specific region.\n\n ### gcloud\n\n\n | **Preview**\n |\n |\n | This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n | of the [Service Specific Terms](/terms/service-terms#1).\n |\n | Pre-GA products and features are available \"as is\" and might have limited support.\n |\n | For more information, see the\n | [launch stage descriptions](/products#product-launch-stages).\n\n \u003cbr /\u003e\n\n You can use the Google Cloud CLI to view the usage and limit of concurrent\n operation quotas.\n\n To use this approach, ensure that you have installed\n the [alpha commands](/sdk/docs/components#alpha_and_beta_components)\n component. If you're using Cloud Shell to interact with Google Cloud, the\n Google Cloud CLI is installed for you.\n\n To view an operation quota, use the following command: \n\n ```\n gcloud alpha services quota list \\\n --service=compute.googleapis.com \\\n --consumer=projects/PROJECT_ID\n ```\n\n Replace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with the ID of the project for which you\n want to view the quota.\n\n These quotas are generally grouped into two categories:\n - Global or regional\n - Per project or per project per operation type\n\n For more information, see [Concurrent operation quota groups](https://cloud.google.com/compute/operations-quota#operation_groups).\n6. Check the usage chart for the quota. If the usage is close to or above the quota limit during the period of error logs, it means that the quota or system limit is exceeded.\n\n To view charts that show current and peak usage, go to the quota and then\n click monitoring **Monitoring**.\n You might need to scroll right to the end of the table.\n\n The monitoring graph will confirm the cause of `rateLimitExceeded` error, with the specific quota/limit. If the current values are above the limit values, it means that the system limit is exceeded.\n Since system limits can't be modified, we recommend the following best practices to reduce the number of concurrent operations.\n\n Some of the best practices are as follows:\n - [Wait for operations to be done](/compute/docs/api/best-practices#wait-for-operations)\n - [Rely on error codes, not error messages](/compute/docs/api/best-practices#rely-on-errors-not-messages)\n - [Minimize client-side retries to preserve API rate limits](/compute/docs/api/best-practices#preserve-API-rate-limits)\n\n Any of the following methods can be used to minimize retries:\n - [Avoid short polling](/compute/docs/api/best-practices#avoid-short-polling)\n - [Use bursting sparingly and selectively](/compute/docs/api/best-practices#limit-bursting)\n - [Always make your calls in a retry loop with exponential backoff](/compute/docs/api/best-practices#retry-with-exponential-backoff)\n - [Use a client-side rate limiter](/compute/docs/api/best-practices#use-client-side-rate-limiter)\n - [Split up your applications across multiple projects](/compute/docs/api/best-practices#multiple-projects)"]]
