Creating a Hive Metastore cluster

Written by

Updated at May 5, 2025

Note

This feature is at the Preview stage.

To learn more about Metastore clusters in Yandex MetaData Hub, see Hive Metastore clusters.

Getting started

To link your service account to a Metastore cluster, make sure your Yandex Cloud account has the iam.serviceAccounts.user role or higher.
Set up a NAT gateway in the subnet the cluster will connect to. It is needed for the cluster to interact with Yandex Cloud services.
Configure the security group.
Create a service account.
Assign the managed-metastore.integrationProvider role to the service account. This role enables the cluster to work with Yandex Cloud services, e.g., Yandex Cloud Logging and Yandex Monitoring, under a service account.

You can also add more roles. Their combination depends on your specific use case. To view the service roles, see the Metastore section, and for all available roles, see this reference.
If you want to save cluster logs to a custom log group, create one.

For more information, see Transferring cluster logs.

Warning

Metastore clusters cannot be edited. Once you create a cluster, you cannot change its settings.

Management console

In the management console, select the folder where you want to create a server.
Select Yandex MetaData Hub.
In the left-hand panel, select the Metastore page.
Click Create cluster.
Enter a name for the cluster. It must be unique within the folder.
(Optional) Enter a cluster description.
(Optional) Add Yandex Cloud labels to break resources into logical groups.
Specify the service account you created earlier.
Under Network settings, select the network and subnet to host the Metastore cluster. Specify the security group you configured previously.
Optionally, configure logging settings:
1. Enable Write logs.
2. Select where to write cluster logs to:
  - Default log group: Select Folder in the Destination field and specify the folder. Logs will be stored in the selected folder's default log group.
  - Custom log group: Select Log group in the Destination field and specify the log group you created earlier.
3. Select the minimum logging level.
  
  Logs of the specified level and higher will be written to the execution log. The available levels are TRACE, DEBUG, INFO, WARN, ERROR, and FATAL. The default level is INFO.
If required, enable protection of the cluster from accidental deletion by a user.

Even with deletion protection enabled, one can still connect to the cluster manually and delete the data.
Click Create.