할당량 값을 초과하거나 할당량 프로젝트를 올바르게 설정하지 않는 등의 여러 가지 이유로 할당량 오류가 발생할 수 있습니다. 오류가 발생할 때 알림을 받으려면 할당량 알림 설정에 설명된 대로 특정 할당량 오류에 대한 커스텀 알림을 만들면 됩니다.
비율 할당량 초과
비율 할당량은 각 서비스에 맞는 사전 정의된 시간 간격이 지나면 재설정됩니다. 자세한 내용은 특정 서비스의 할당량 문서를 참조하세요.
할당량 값 초과
프로젝트에서 서비스 사용 중에 최대 할당량 값을 초과하면 Google Cloud에서 서비스에 액세스한 방법에 따라 오류를 반환합니다.
API 요청 시 할당량 값을 초과하면 Google Cloud 에서 HTTP 413 REQUEST ENTITY TOO LARGE 상태 코드를 반환합니다.
프로덕션 환경에서 BigQuery 기존 스트리밍 API를 사용할 때 HTTP 요청이 10MB보다 크면 413 REQUEST ENTITY TOO LARGE 상태 코드가 수신될 수 있습니다. 초당 300MB를 초과하는 경우에도 이 오류가 발생할 수 있습니다. 자세한 내용은 스트리밍 삽입을 참조하세요.
HTTP/REST 요청 시 할당량 값을 초과하면 Google Cloud 에서 HTTP 429 TOO MANY REQUESTS 상태 코드를 반환합니다.
Compute Engine 할당량을 초과하면 요청이 API, HTTP/REST, gRPC에서 시작되었는지 여부에 관계없이 일반적으로 Google Cloud 에서 HTTP 403 QUOTA_EXCEEDED 상태 코드를 반환합니다. 할당량이 비율 할당량이면 403 RATE_LIMIT_EXCEEDED가 반환됩니다.
gRPC를 사용 시 할당량 값을 초과하면 Google Cloud 에서 ResourceExhausted 오류를 반환합니다. 이 오류가 표시되는 방식은 서비스에 따라 다릅니다.
Google Cloud CLI 명령어를 사용하여 할당량 값을 초과하면 gcloud CLI가 할당량 초과 오류 메시지를 출력하고 종료 코드 1을 반환합니다.
서비스 출시 중 QUOTA_EXCEEDED 메시지가 표시되면 다음 섹션을 참조하세요.
서비스 출시 중 할당량 값 초과
경우에 따라Google Cloud 에서 리소스 및 API의 기본 할당량 값을 변경합니다. 이러한 변경사항은 점진적으로 발생합니다. 따라서 새 기본 할당량이 출시되었을 때 Google Cloud 콘솔에 표시되는 할당량 값은 사용자에게 제공되는 새 할당량 값을 반영하지 않을 수 있습니다.
할당량 적용이 진행 중인 경우 The future limit is the new default quota that will be available after a
service rollout completes.라는 오류 메시지가 표시될 수 있습니다. 이 오류 메시지가 표시되면 인용된 할당량 값과 향후 값은, Google Cloud 콘솔에 표시되는 내용이 다르더라도 올바르다는 의미입니다.
자세한 내용을 보려면 감사 로그를 확인하고 QUOTA_EXCEEDED 메시지를 확인합니다.
할당량 프로젝트를 설정하지 않으면 gcloud CLI 명령어에서 다음과 같은 오류를 반환할 수 있습니다.
PERMISSION_DENIED: Your application is authenticating by using local Application Default Credentials.
The cloudquotas.googleapis.com API requires a quota project, which is not set by default.
이 문제를 해결하려면 gcloud CLI 명령어에 --billing-project 플래그를 추가하여 할당량 프로젝트를 명시적으로 설정하거나 gcloud config set billing/quota_project CURRENT_PROJECT를 다시 실행하여 할당량 프로젝트를 현재 프로젝트로 설정합니다.
[[["이해하기 쉬움","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-04-14(UTC)"],[[["\u003cp\u003eQuota errors can occur due to exceeding quota values, rate quotas, or incorrect project quota settings, each with distinct error codes and messages.\u003c/p\u003e\n"],["\u003cp\u003eDuring service rollouts, the quota value displayed in the Google Cloud console might differ from the actual available quota, and the system will provide a \u003ccode\u003eQUOTA_EXCEEDED\u003c/code\u003e error with a \u003ccode\u003efutureLimit\u003c/code\u003e value.\u003c/p\u003e\n"],["\u003cp\u003eAPI request errors such as \u003ccode\u003eUser credentials not supported by this API\u003c/code\u003e, \u003ccode\u003eAPI not enabled in the project\u003c/code\u003e, or \u003ccode\u003eNo quota project set\u003c/code\u003e often indicate issues with the quota project configuration.\u003c/p\u003e\n"],["\u003cp\u003eWhen using the gcloud CLI, ensure it's properly installed, initialized, and updated, and the quota project must be set correctly to avoid errors like \u003ccode\u003ePERMISSION_DENIED\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo mitigate errors, users can set up custom alerts for specific quota errors, view audit logs for \u003ccode\u003eQUOTA_EXCEEDED\u003c/code\u003e messages, and request a quota adjustment if necessary.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot quota errors\n\nYou might receive quota errors for a number of reasons, such as exceeding quota\nvalues or not setting the quota on a project correctly. If you want to be alerted\nwhen errors happen, you can create custom alerts for specific\nquota errors, as described in\n[Set up quota alerts](/docs/quotas/set-up-quota-alerts).\n\nExceeding rate quotas\n---------------------\n\nRate quotas reset after a predefined time interval that is specific to each\nservice. For more information, see the quotas documentation for the specific\nservice.\n\nExceeding quota values\n----------------------\n\nIf your project exceeds its maximum quota value while using a service, Google Cloud\nreturns an error based on how you accessed the service:\n\n- If you exceed a quota value with an API request, Google Cloud returns an HTTP `413 REQUEST ENTITY TOO LARGE` status code. Note that when using the BigQuery legacy streaming API in a production environment, you may receive a `413 REQUEST ENTITY TOO LARGE` status code if your HTTP requests are larger than 10 MB. You may also receive this error if you exceed 300 MB per second. For more information see [Streaming inserts.](/bigquery/quotas#streaming_inserts)\n- If you exceeded a quota value with an HTTP/REST request, Google Cloud returns an HTTP `429 TOO MANY REQUESTS` status code.\n- If you exceed a quota for Compute Engine, Google Cloud typically returns an HTTP `403 QUOTA_EXCEEDED` status code, whether it was from API, HTTP/REST, or gRPC. If the quota is a rate quota, then `403 RATE_LIMIT_EXCEEDED` is returned.\n- If you exceeded a quota value using [gRPC](https://grpc.io), Google Cloud returns a `ResourceExhausted` error. How this error appears to you depends on the service.\n- If you exceeded a quota value using a Google Cloud CLI command, the gcloud CLI outputs a quota-exceeded error message and returns with the exit code `1`.\n- If you received a `QUOTA_EXCEEDED` message during a service rollout, see the following section.\n\nExceeding quota values during a service rollout\n-----------------------------------------------\n\nGoogle Cloud sometimes changes the default quota values for resources\nand APIs. These changes take place gradually, which means that during the\nrollout of a new default quota, the quota value that appears in the Google Cloud console\nmight not reflect the new quota value that is available to you.\n\nIf a quota rollout is in progress, you may receive an error message that states\n`The future limit is the new default quota that will be available after a\nservice rollout completes.` If you see this error message, the cited quota value\nand future value are correct, even if what appears in the Google Cloud console\nis different.\n\n- For additional information, [view the audit logs](/logging/docs/audit#view-logs)\n and look for a `QUOTA_EXCEEDED` message.\n\n \"status\": {\n ...\n \"message\": \"QUOTA_EXCEEDED\",\n \"details\": [\n {\n ...\n \"value\": {\n \"quotaExceeded\": {\n ...\n \"futureLimit\": \u003cvar translate=\"no\"\u003eFUTUREVALUE\u003c/var\u003e\n }\n }\n }\n ]\n },\n\n- To view charts that show current and peak usage,\n in the Google Cloud console, go to the\n [**IAM \\& Admin \\\u003e Quotas \\& System Limits**](https://console.cloud.google.com/quotas?project=_)\n page and then click monitoring**Monitoring**.\n You might need to go to the end of the table.\n\n- If you need more quota, you can\n [request a quota adjustment](/docs/quotas/help/request_increase).\n\nExceeding project quota\n-----------------------\n\nFor more information about requesting additional *project quotas* , refer to the\n[Project quota requests](https://support.google.com/cloud/answer/6330231)\nsupport article.\n\nAPI error messages\n------------------\n\nIf your quota project (also called a billing project) isn't set correctly, API\nrequests might return error messages that are similar to the following:\n\n- `User credentials not supported by this API`\n- `API not enabled in the project`\n- `No quota project set`\n\nThese and other errors can often be fixed by setting the quota project.\nFor more information, see [Quota project overview](/docs/quotas/quota-project).\n\nGoogle Cloud CLI errors\n-----------------------\n\nThis section describes common issues encountered when getting started with the\nGoogle Cloud CLI (gcloud CLI).\n\n### Install and initialize\n\nTo use the gcloud CLI for Cloud Quotas, be sure to install and\ninitialize components:\n\n1. [Install](/sdk/docs/install) the gcloud CLI.\n\n If you're using Cloud Shell, you can skip this step because\n gcloud CLI comes pre-installed.\n2. [Initialize](/sdk/docs/initializing) the gcloud CLI.\n\n3. [Install the beta component](/sdk/docs/components#alpha_and_beta_components)\n by running the following command:\n\n gcloud components install beta\n\n### Set your quota project\n\nIf you haven't set your quota project, gcloud CLI commands might\nreturn an error like the following: \n\n PERMISSION_DENIED: Your application is authenticating by using local Application Default Credentials.\n The cloudquotas.googleapis.com API requires a quota project, which is not set by default.\n\nTo resolve this issue, add the `--billing-project` flag on your\ngcloud CLI command to explicitly set the quota project, or rerun\n`gcloud config set billing/quota_project CURRENT_PROJECT` to set the quota project\nas the current project.\n\nFor more information, see the following:\n\n- [Set the quota project programmatically](/docs/quotas/set-quota-project#set-project-programmatically).\n- [Set the billing project](/sdk/gcloud/reference#--billing-project) through the gcloud CLI.\n\n### Update gcloud CLI components\n\nIf you receive an error that the quotas command contains an `Invalid choice`,\nyou might have an older version of the gcloud CLI installed.\nUpdate the gcloud CLI components with the following command: \n\n gcloud components update\n\nFor more details about `gcloud beta quotas` commands and flags, see the\n[gcloud beta quotas](/sdk/gcloud/reference/beta/quotas)\nsection of the Google Cloud CLI reference."]]
