Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menjelaskan kuota operasi serentak untuk Compute Engine.
Kuota operasi serentak
Kuota operasi serentak menentukan jumlah operasi yang sedang berlangsung atau
serentak yang dapat terjadi pada titik waktu tertentu. Setiap permintaan API yang membuat, mengubah, atau menghapus resource Compute Engine tunduk pada pemeriksaan batas operasi serentak untuk memastikan bahwa jumlah total operasi yang sedang berlangsung pada titik waktu tertentu tidak melebihi batas yang ditentukan untuk operasi tersebut.
Error batas operasi serentak terlampaui
Jika project Anda melebihi batas operasi serentak untuk operasi yang
sedang berlangsung, Anda akan menerima error 403 dengan alasan rateLimitExceeded.
Respons API error terlihat mirip dengan yang berikut ini:
METHOD_NAME dalam error mewakili
metode API yang batas kapasitasnya terlampaui. Contoh, v1.compute.instances.stop.
Grup kuota operasi serentak
Bagian ini menjelaskan batas untuk berbagai operasi Compute Engine yang sedang berlangsung atau serentak.
Kuota operasi global
Operasi global serentak memakai batas global yang ditentukan
untuk jenis operasi per project. Tabel berikut mencantumkan kuota global untuk operasi yang sedang berlangsung dan metrik terkait.
Anda dapat melihat kuota untuk operasi global menggunakan Google Cloud konsol,
Google Cloud CLI, dan Service Usage API. Untuk mengetahui informasi selengkapnya, lihat
Melihat kuota dan batas operasi serentak.
Nama kuota
Deskripsi
Nama metrik
Metode yang menggunakan kuota ini
Concurrent global operations per project
Membatasi jumlah total operasi global serentak untuk sebuah project.
Kuota operasi serentak default adalah 500 operasi yang sedang berlangsung
per project, kecuali untuk metode berikut, yang memiliki batas default yang berbeda:
Operasi regional serentak memakai batas regional yang ditentukan
untuk jenis operasi per project di region tertentu.
Tabel berikut mencantumkan kuota regional untuk operasi yang sedang berlangsung dan metrik terkait.
Anda dapat melihat kuota untuk operasi regional
menggunakan Google Cloud konsol,
Google Cloud CLI, dan Service Usage API. Untuk mengetahui informasi selengkapnya, lihat
Melihat kuota dan batas operasi serentak.
Nama kuota
Deskripsi
Nama metrik
Metode yang menggunakan kuota ini
Concurrent regional operations per project
Membatasi jumlah total operasi regional serentak untuk sebuah project.
URL permintaan HTTP berisi regions atau zones untuk metode ini.
Misalnya, metode instances.insert: POST /compute/v1/projects/{project}/zones/{zone}/instances
Concurrent regional operations per project operation type
Membatasi jumlah operasi regional serentak per project per jenis operasi.
Kuota operasi serentak default adalah 500 operasi yang sedang berlangsung
per project per region, kecuali untuk metode berikut, yang memiliki
batas default yang berbeda:
Halaman Quotas mencantumkan semua penggunaan dan batas kuota untuk project Anda.
Secara default, daftar ini diurutkan untuk menampilkan kuota yang paling banyak digunakan terlebih dahulu,
yang membantu Anda melihat batas yang berisiko terlampaui.
Untuk memfilter daftar dan melihat penggunaan serta batas untuk kuota tertentu,
pilih Kuota atau Metrik di kolom Filter.
Misalnya, pilih Kuota Concurrent global operations per project operation type
untuk melihat penggunaan kuota untuk metode global per jenis operasi.
Untuk memfilter kuota untuk operasi tertentu, tambahkan Dimensi ke kueri filter
dan pilih operation_type. Misalnya, pilih firewalls_insert
untuk melihat penggunaan dan batas kuota untuk operasi firewalls.insert.
gcloud
Anda dapat menggunakan Google Cloud CLI untuk melihat penggunaan dan batas kuota operasi serentak.
Untuk menggunakan pendekatan ini, pastikan Anda telah menginstal komponen perintah alfa. Jika Anda menggunakan Cloud Shell untuk berinteraksi dengan Google Cloud, Google Cloud CLI akan diinstal untuk Anda.
Untuk melihat kuota, gunakan perintah berikut:
gcloud alpha services quota list \
--service=compute.googleapis.com \
--consumer=projects/PROJECT_ID
Ganti PROJECT_ID dengan ID project yang ingin Anda
lihat kuotanya.
Praktik terbaik
Checklist berikut merangkum praktik terbaik untuk mengurangi error
batas operasi serentak yang tidak memadai:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[[["\u003cp\u003eConcurrent operation quotas define the maximum number of in-flight operations allowed for creating, modifying, or deleting Compute Engine resources at any given time.\u003c/p\u003e\n"],["\u003cp\u003eExceeding these concurrent operation limits results in a \u003ccode\u003e403\u003c/code\u003e error with the reason \u003ccode\u003erateLimitExceeded\u003c/code\u003e, indicating the project has surpassed the allowed number of simultaneous operations.\u003c/p\u003e\n"],["\u003cp\u003eGlobal and regional operation quotas limit concurrent operations, and each can be viewed in the Google Cloud console or using the Google Cloud CLI.\u003c/p\u003e\n"],["\u003cp\u003eThe error details provide information such as the project ID, the quota metric exceeded, the quota limit name, the operation type, and the location, which are only available through the API response.\u003c/p\u003e\n"],["\u003cp\u003eBest practices for reducing concurrent operation errors include waiting for operations to complete, minimizing client-side retries, and implementing exponential backoff for retries.\u003c/p\u003e\n"]]],[],null,["# Compute Engine concurrent operation quotas\n\n*** ** * ** ***\n\nThis document describes the concurrent operation quotas for Compute Engine.\n\nConcurrent operation quotas\n---------------------------\n\nConcurrent operation quotas define the number of in-flight or concurrent\noperations that can occur at any point of time. Any API request that creates,\nmodifies, or deletes a Compute Engine resource is subject to a concurrent\noperation limit check to ensure that the total number of in-flight operations\nat any point of time does not exceed the limit specified for that operation.\n\n### Concurrent operation limit exceeded error\n\nIf your project exceeds the concurrent operation limit for any in-flight\noperation, you receive a `403` error with the reason `rateLimitExceeded`.\n\nThe API response of the error looks similar to the following:\n\n\u003cbr /\u003e\n\n```\n \"error\": {\n \"code\": 403,\n \"message\": \"Rate Limit Exceeded\",\n \"errors\": [\n {\n \"message\": \"Rate Limit Exceeded\",\n \"domain\": \"usageLimits\",\n \"reason\": \"rateLimitExceeded\",\n ...\n ...\n }\n ],\n \"details\": [\n {\n \"@type\": \"type.googleapis.com/google.rpc.ErrorInfo\",\n \"reason\": \"CONCURRENT_OPERATIONS_QUOTA_EXCEEDED\",\n \"domain\": \"compute.googleapis.com\",\n \"metadata\": {\n \"containerType\": \"PROJECT\",\n \"containerId\": \"PROJECT_ID\",\n \"quotaMetric\": \"QUOTA_METRIC\",\n \"quotaLimit\": \"QUOTA_LIMIT\",\n \"operationType\": \"OPERATION_TYPE\",\n \"location\": \"global | REGION\"\n }\n },\n {\n \"@type\": \"type.googleapis.com/google.rpc.Help\",\n \"links\": [\n {\n \"description\": \"Concurrent operations quota documentation.\",\n \"url\": \"https://cloud.google.com/compute/operations-quota#concurrent_operation_limits\"\n }\n ]\n },\n ...\n ... \n```\n\n\u003cbr /\u003e\n\nThe error details contain the following values:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project in which\n the quota exceeds the limit.\n\n- \u003cvar translate=\"no\"\u003eQUOTA_METRIC\u003c/var\u003e: the metric for the concurrent quota\n that exceeds the limit. It can be one of the following:\n\n - `compute.googleapis.com/global_concurrent_operations`\n - `compute.googleapis.com/regional_concurrent_operations`\n- \u003cvar translate=\"no\"\u003eQUOTA_LIMIT\u003c/var\u003e: the limit name of the concurrent quota.\n It can be one of the following:\n\n - `GlobalConcurrentOperationsPerProject`\n - `GlobalConcurrentOperationsPerProjectOperationType`\n - `RegionalConcurrentOperationsPerProject`\n - `RegionalConcurrentOperationsPerProjectOperationType`\n- \u003cvar translate=\"no\"\u003eOPERATION_TYPE\u003c/var\u003e: the global or regional operation for\n which the quota exceeds the limit. For a list of operations, see\n [Concurrent operation quota groups](#operation_groups).\n\n- The `location` can be one of the following:\n\n - `global`: specifies that the limit exceeded for global operation quota\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: specifies the region where the limit exceeded for the operation quota\n\nThe detailed error logs are returned only through API response. Error in Logs Explorer is similar to the following:\n\n\u003cbr /\u003e\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 ...\n ... \n```\n\n\u003cbr /\u003e\n\nThe \u003cvar translate=\"no\"\u003eMETHOD_NAME\u003c/var\u003e in the error represents the\nAPI method for which the rate limit exceeded. For example, `v1.compute.instances.stop`.\n\n### Concurrent operation quota groups\n\nThis section describes the limits for various Compute Engine in-flight or\nconcurrent operations.\n\n#### Global operation quotas\n\nConcurrent global operations consume a global limit that is specified\nfor operation types per project. The following table lists the global quotas for\nin-flight operations and the corresponding metrics.\n\nYou can view the quota for global operations by using the Google Cloud console,\nGoogle Cloud CLI, and Service Usage API. For more information, see\n[View concurrent operation quotas and limits](#view_quota_limits).\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n#### Regional operation quotas\n\nConcurrent regional operations consume a regional limit that is specified\nfor operation types per project in a given region.\n\nThe following table lists the regional quotas for in-flight operations and\nthe corresponding metrics.\n\nYou can view the quota for regional operations\nby using the Google Cloud console,\nGoogle Cloud CLI, and Service Usage API. For more information, see\n[View concurrent operation quotas and limits](#view_quota_limits).\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n### View concurrent operation quotas and limits\n\nTo view the quota usage and limits in a project, do the following: \n\n### Console\n\n1. 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 all 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.\n2. To filter the list and to view the usage and limit for any specific quota,\n select the **Quota** or **Metric** in the **Filter** field.\n\n For example, select the Quota `Concurrent global operations per project operation type`\n to see the quota usage for global methods per operation type.\n\n To filter the quota for a specific operation, add **Dimensions** to the filter query\n and select the **operation_type** . For example, select `firewalls_insert`\n to see the quota usage and limit for `firewalls.insert` operation.\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\nYou can use the Google Cloud CLI to view the usage and limit of concurrent\noperation quotas.\n\nTo use this approach, ensure that you have installed\nthe [alpha commands](/sdk/docs/components#alpha_and_beta_components)\ncomponent. If you're using Cloud Shell to interact with Google Cloud, the\nGoogle Cloud CLI is installed for you.\n\nTo view the quota, use the following command: \n\n gcloud alpha services quota list \\\n --service=compute.googleapis.com \\\n --consumer=projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e\n\nReplace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with the ID of the project for which you\nwant to view the quota.\n\n### Best practices\n\nThe following checklist summarizes the best practices for reducing insufficient\nconcurrent operation limit errors:\n\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 - [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)\n\nWhat's next\n-----------\n\n- Read about [Cloud Quotas](/docs/quotas/overview)."]]
