Stay organized with collections
Save and categorize content based on your preferences.
The following sections explain quotas and limits for Dataproc Metastore.
To change a quota, request additional quota by
using the Google Cloud console. Limits generally cannot be increased unless
specifically noted.
When a project violates Google Cloud service policy, its per-region service quota is significantly lowered.
Metadata storage for Dataproc Metastore services
Item
Quotas and limits
Notes
Metadata storage per Developer tier service
10 GB
Metadata storage per Enterprise tier service
1 TB
Queries per second for Dataproc Metastore projects
Item
Quotas and limits
Notes
Queries per second (QPS) per project
20 QPS
Queries per second (QPS) per project per user
5 QPS
Maintenance queries per second (QPS) per project
20 QPS
The following Hive Metastore requests consume this quota:
createTable
createDatabase
deleteTable
deleteDatabase
Job timeout limit for Dataproc Metastore
Item
Quotas and limits
Notes
Job timeout limit for export/backup/restore
1 hour
Job timeout limit for import
3 hours
Quotas management
Dataproc Metastore enforces quotas on resource usage for a variety
of reasons. For example, quotas protect the community of Google Cloud
users by preventing unforeseen spikes in usage. Quotas also help users who are
exploring Google Cloud with the
free tier
to stay within their trial.
All projects start with the same quotas, which you can change by
requesting additional quota. Some
quotas may increase automatically based on your use of a product.
Permissions
To view quotas or request quota increases, Identity and Access Management (IAM) principals
need one of the following roles.
On the Quotas page, select the quotas that you want to change.
At the top of the page, click
editEdit quotas.
Fill out your name, email, and phone number, and then click Next.
Fill in your quota request, and then click Done.
Submit your request.
Resource availability
Each quota represents a maximum number for a particular type of resource that
you can create, provided that resource is available. It's important to note that
quotas do not guarantee resource availability. Even if you have available
quota, you won't be able to create a new resource if it is not available.
For example, you might have sufficient quota to create a new regional, external
IP address in the us-central1 region, but that would not be
possible if there were no available external IP addresses in that region. Zonal
resource availability can also affect your ability to create a new resource.
Situations where resources are unavailable in an entire region are rare; however,
resources within a zone can be depleted from time to time, typically without
impact to the service level agreement (SLA) for the type of resource. For more
information, review the relevant SLA for the resource.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eDataproc Metastore enforces quotas on resource usage to protect Google Cloud users and help users on the free tier stay within their limits.\u003c/p\u003e\n"],["\u003cp\u003eQuotas for Dataproc Metastore services include limits on the number of services per region (20) and multi-region (5), as well as metadata storage per service tier, such as 10 GB for \u003ccode\u003eDeveloper\u003c/code\u003e tier and 1 TB for \u003ccode\u003eEnterprise\u003c/code\u003e tier.\u003c/p\u003e\n"],["\u003cp\u003eThere are different queries per second (QPS) limits per project, with 20 QPS for general usage, 5 QPS per user, and 20 QPS for maintenance queries, such as \u003ccode\u003ecreateTable\u003c/code\u003e or \u003ccode\u003edeleteDatabase\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eJob timeout limits are also defined, with 1 hour for export/backup/restore jobs and 3 hours for import jobs.\u003c/p\u003e\n"],["\u003cp\u003eYou can request additional quota via the Google Cloud console, and quota changes generally take 24 to 48 hours to be processed.\u003c/p\u003e\n"]]],[],null,["# Quotas and limits\n\nThe following sections explain quotas and limits for Dataproc Metastore.\nTo change a quota, [request additional quota](#request-additional-quota) by\nusing the Google Cloud console. Limits generally cannot be increased unless\nspecifically noted.\n\nQuotas and limits\n-----------------\n\n### Dataproc Metastore services\n\n### Metadata storage for Dataproc Metastore services\n\n### Queries per second for Dataproc Metastore projects\n\n### Job timeout limit for Dataproc Metastore\n\nQuotas management\n-----------------\n\nDataproc Metastore enforces quotas on resource usage for a variety\nof reasons. For example, quotas protect the community of Google Cloud\nusers by preventing unforeseen spikes in usage. Quotas also help users who are\nexploring Google Cloud with the\n[free tier](/free/docs/gcp-free-tier)\nto stay within their trial.\n\nAll projects start with the same quotas, which you can change by\n[requesting additional quota](#request-additional-quota). Some\nquotas may increase automatically based on your use of a product.\n\n### Permissions\n\nTo view quotas or request quota increases, Identity and Access Management (IAM) principals\nneed one of the following roles.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n### Check your quota\n\n### Console\n\n1. In the Google Cloud console, go to the **Quotas** page.\n\n [Go to the Quotas page](https://console.cloud.google.com/iam-admin/quotas)\n2. To search for the quota that you want to update, use the **Filter table**.\n If you don't know the name of the quota, use the links on this page instead.\n\n### Errors when exceeding your quota\n\nIf you exceed a quota with a `gcloud` command,\n`gcloud` outputs a `quota exceeded` error\nmessage and returns with the exit code `1`.\n\nIf you exceed a quota with an API request, Google Cloud returns the\nfollowing HTTP status code: `HTTP 413 Request Entity Too Large`.\n\n### Request additional quota\n\nRequest additional quota from the **Quotas** page in the Google Cloud console.\nQuota requests take 24 to 48 hours to process. \n\n### Console\n\n1. In the Google Cloud console, go to the **Quotas** page.\n\n [Go to the Quotas page](https://console.cloud.google.com/iam-admin/quotas)\n2. On the **Quotas** page, select the quotas that you want to change.\n\n3. At the top of the page, click\n edit**Edit quotas**.\n\n4. Fill out your name, email, and phone number, and then click **Next**.\n\n5. Fill in your quota request, and then click **Done**.\n\n6. Submit your request.\n\n### Resource availability\n\nEach quota represents a maximum number for a particular type of resource that\nyou can create, provided that resource is available. It's important to note that\nquotas *do not* guarantee resource availability. Even if you have available\nquota, you won't be able to create a new resource if it is not available.\n\nFor example, you might have sufficient quota to create a new regional, external\nIP address in the `us-central1` region, but that would not be\npossible if there were no available external IP addresses in that region. Zonal\nresource availability can also affect your ability to create a new resource.\n\nSituations where resources are unavailable in an entire region are rare; however,\nresources within a zone can be depleted from time to time, typically without\nimpact to the service level agreement (SLA) for the type of resource. For more\ninformation, review the relevant SLA for the resource.\n\nWhat's next\n-----------\n\n- Learn more about [Dataproc Metastore resources](/dataproc-metastore/docs/resources).\n- Learn about [Dataproc Metastore pricing](/dataproc-metastore/pricing)."]]
