Stay organized with collections
Save and categorize content based on your preferences.
When you create a Dataproc Metastore service, you can choose to use
a Dataproc Metastore 2 service or a Dataproc Metastore 1
service.
This document explains how to control resource consumption for
Dataproc Metastore 2.
Scaling factors and editions
Dataproc Metastore 2 uses scaling factors and editions (workloads)
to handle varying levels of stability and workloads. You select your scaling
factor and edition when you create a Dataproc Metastore service.
After you create your Dataproc Metastore service,
you can scale the service up or down by modifying the scaling factor. Scaling
factors range from small to XLarge and are represented by a number
ranging from 0.1 to 6.0.
Dataproc Metastore 2 also supports autoscaling. If you turn on autoscaling,
you set a minimum scaling factor and a maximum scaling factor. After these
parameters are set, your service automatically increases or decreases resource
consumption to run workloads. Autoscaling is only available for single region
Dataproc Metastore instances.
Dataproc Metastore is present in several regions that have fewer
resources available than others. These regions constrain the maximum scaling
factor to 1 and don't support autoscaling. The following regions are
considered resource constrained regions by Dataproc Metastore:
[[["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-07 UTC."],[[["\u003cp\u003eDataproc Metastore 2 allows users to control resource consumption through scaling factors and editions, which handle different levels of stability and workloads.\u003c/p\u003e\n"],["\u003cp\u003eScaling factors for Dataproc Metastore 2 range from \u003ccode\u003esmall\u003c/code\u003e to \u003ccode\u003eXLarge\u003c/code\u003e, represented numerically from \u003ccode\u003e0.1\u003c/code\u003e to \u003ccode\u003e6.0\u003c/code\u003e, and can be modified after service creation to scale the service up or down.\u003c/p\u003e\n"],["\u003cp\u003eDataproc Metastore 2 also offers autoscaling for single region instances, allowing automatic adjustment of resource consumption based on a set minimum and maximum scaling factor.\u003c/p\u003e\n"],["\u003cp\u003eUsers have the option to choose between a Dataproc Metastore 1 service or a Dataproc Metastore 2 service when creating a Dataproc Metastore service.\u003c/p\u003e\n"]]],[],null,[]]