The price of a Dataproc Metastore 2 is determined by the following calculation:

Scaling factor * Edition (price per hour) * Number of hours running

After you create your Dataproc Metastore service, you can scale the service up or down by modifying the scaling factor. You can also turn on autoscaling so Dataproc Metastore services can use the appropriate scaling factor based on demand.

The following table lists the available editions and cost per hour.

Dataproc Metastore 1 calculates pricing based on the service tier that you choose.

Service tier pricing lets you choose a predetermined amount of resources that your Dataproc Metastore service uses. By doing so, you can run a Dataproc Metastore service at a predictable, fixed cost.

With service tier pricing, you are charged each hour for each of your Dataproc Metastore service. The rate for each service depends on the type of service tier used for the service.

Service tier pricing is available on Dataproc Metastore services that use either the MySQL or Spanner database type.

• Developer is the default tier. The default tier is good for low-cost proof-of-concept solutions as it provides limited scalability and no fault tolerance.
• Enterprise tier provides flexible scalability, fault tolerance, and multi-zone high availability. The enterprise tier can handle heavy Dataproc Metastore workloads.

Charges apply even if you don't run any Managed Service for Apache Spark workloads against your Dataproc Metastore instance.

Note: You are not charged for importing or exporting service metadata. However, you incur any Cloud Storage bucket storage costs.