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.
For more information about editions and scaling factors, see Scaling factors and workloads.
Autoscaling
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.
For more information on setting up autoscaling, see Create an autoscaling service.
Resource constrained regions
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:
australia-southeast2europe-southwest1europe-west8europe-west9europe-west12southamerica-west1us-east5us-south1me-central1me-central2me-west1