Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex MetaData Hub
  • About Yandex MetaData Hub
    • Getting started
      • Getting information about clusters
      • Creating a cluster
      • Updating a cluster
      • Stopping and restarting a cluster
      • Configuring security groups
      • Connecting Yandex Data Processing to Apache Hive™ Metastore
      • Exporting and importing a cluster
      • Connecting to a Yandex Object Storage bucket with a bucket policy
      • Transferring logs to Cloud Logging
      • Managing cluster access
      • Maintenance
      • Deleting a cluster
    • Service roles for access management
    • Troubleshooting
    • Terraform reference
    • Audit Trails events
  • Access management
  • Quotas and limits
  • Pricing policy
  • Public materials
  • Release notes

In this article:

  • Getting a list of maintenance jobs
  • Getting cluster maintenance logs
  • Moving scheduled maintenance
  • Starting scheduled maintenance immediately
  • Configuring a maintenance window
  1. Apache Hive™ Metastore
  2. Step-by-step guides
  3. Maintenance

Apache Hive™ Metastore cluster maintenance

Written by
Yandex Cloud
Updated at August 5, 2026
View in Markdown
  • Getting a list of maintenance jobs
  • Getting cluster maintenance logs
  • Moving scheduled maintenance
  • Starting scheduled maintenance immediately
  • Configuring a maintenance window

You can manage maintenance of a Apache Hive™ Metastore cluster.

Getting a list of maintenance jobsGetting a list of maintenance jobs

Management console
  1. In the management console, navigate to the relevant folder.

  2. Navigate to Yandex MetaData Hub.

  3. In the left-hand panel, select  Metastore.

  4. Click the name of your cluster and select the Maintenance tab.

    To view maintenance jobs with a specific status, select the status you want from the Status field above the list of maintenance jobs. To find a specific maintenance job, enter its ID or task name in the field above the list of maintenance jobs.

Getting cluster maintenance logsGetting cluster maintenance logs

Management console
  1. In the management console, navigate to the relevant folder.
  2. Navigate to Yandex MetaData Hub.
  3. In the left-hand panel, select  Metastore.
  4. Click the name of your cluster and select the Maintenance tab.
  5. Select a maintenance job. The maintenance page will open.
  6. Click Task logs.

Moving scheduled maintenanceMoving scheduled maintenance

Maintenance with the Planned status is scheduled for the date and time specified in the Start date column. You can reschedule it to a new date and time as needed.

To reschedule maintenance for a new date and time:

Management console
  1. In the management console, navigate to the relevant folder.

  2. Navigate to Yandex MetaData Hub.

  3. In the left-hand panel, select  Metastore.

  4. Click the name of your cluster and select the Maintenance tab.

  5. Click next to the maintenance with the Planned status and select Postpone.

  6. Select the reschedule type for the planned maintenance:

    • Next window: Reschedule to the next maintenance window.

    • Choose date (UTC): Reschedule to a specific date and time.

      For this option, select the date and UTC time interval.

      Maintenance can be postponed for a maximum of two weeks from the original scheduled date.

  7. Click Reschedule.

Starting scheduled maintenance immediatelyStarting scheduled maintenance immediately

If you need to, you can perform a maintenance with the Planned status immediately without waiting for the time specified in the Start date column.

To run a scheduled cluster maintenance job immediately:

Management console
  1. In the management console, navigate to the relevant folder.
  2. Navigate to Yandex MetaData Hub.
  3. In the left-hand panel, select  Metastore.
  4. Click the name of your cluster and select the Maintenance tab.
  5. In the maintenance row, click and select Carry out now.

Configuring a maintenance windowConfiguring a maintenance window

Management console
CLI
Terraform
REST API
gRPC API
  1. In the management console, navigate to the relevant folder.

  2. Navigate to Yandex MetaData Hub.

  3. In the left-hand panel, select  Metastore.

  4. Click the name of your cluster and select the Maintenance tab.

  5. Click Configure the maintenance window in the top-right corner of the page.

  6. Select cluster maintenance time:

    • To allow maintenance at any time, select At any time (default).
    • To specify the preferred maintenance start time, select By schedule and specify the day of the week and the UTC time interval. For example, you can choose the cluster's least busy time.

    Both active and stopped clusters are subject to maintenance operations. These may include installing Apache Hive™ Metastore updates and patches as well as other maintenance works.

  7. Click Save.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

To configure a maintenance window:

  1. See the description of the CLI command for updating cluster settings:

    yc managed-metastore cluster update --help
    
  2. Configure the maintenance window:

    yc managed-metastore cluster update <cluster_name_or_ID> \
      --maintenance-window type=<maintenance_type>,`
                          `day=<day_of_week>,`
                          `hour=<sequence_number_of_hour_interval>
    

    Where:

    • <cluster_name_or_ID>: Cluster name or ID which you can get with the list of clusters in the folder.

    • --maintenance-window: Maintenance window settings that apply to both running and stopped clusters. The type setting defines the maintenance type:

      • anytime: Any time (default).
      • weekly: On a schedule. For this value, also specify the following:
        • day: Day of week, i.e., MON, TUE, WED, THU, FRI, SAT, or SUN.

        • hour: Sequence number of UTC hour interval, from 1 to 24.

          For example, 1 stands for the interval from 00:00 to 01:00, and 5, from 04:00 to 05:00.

  1. Open the current Terraform configuration file with the infrastructure plan.

    To learn how to create this file, see Creating a cluster.

    For the complete list of configurable Apache Hive™ Metastore cluster fields, see this Terraform provider guide.

  2. To set up a maintenance window, add the maintenance_window section to the cluster description:

    resource "yandex_metastore_cluster" "<local_cluster_name>" {
      ...
      maintenance_window = {
        type = "<maintenance_type>"
        day  = "<day_of_week>"
        hour = <sequence_number_of_hour_interval>
      }
      ...
    }
    

    Where:

    • type: Maintenance type. The possible values include:

      • ANYTIME: Any time.
      • WEEKLY: On a schedule.
    • day: Day of week for the WEEKLY type, i.e., MON, TUE, WED, THU, FRI, SAT, or SUN.

    • hour: UTC hour interval for the WEEKLY type, from 1 to 24.

      For example, 1 stands for the interval from 00:00 to 01:00, and 5, from 04:00 to 05:00.

  3. Make sure the settings are correct.

    1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

    2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

  4. Confirm updating the resources.

    1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply
        
      2. Confirm updating the resources.

      3. Wait for the operation to complete.

  1. Get an IAM token for API authentication and put it into an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Call the Cluster.Update method, e.g., via the following cURL request:

    curl \
      --request PATCH \
      --header "Authorization: Bearer $IAM_TOKEN" \
      --header "Content-Type: application/json" \
      --url 'https://metastore.api.cloud.yandex.net/managed-metastore/v1/clusters/<cluster_ID>' \
      --data '{
               "updateMask": "maintenanceWindow",
               "maintenanceWindow": {
                 "weeklyMaintenanceWindow": {
                   "day": "<day_of_week>",
                   "hour": "<sequence_number_of_hour_interval>"
                 }
               }
             }'
    

    Where:

    • <cluster_ID>: Cluster ID which you can get with the list of clusters in the folder.

    • updateMask: Comma-separated string of settings to update.

      In this example, only the maintenanceWindow setting is provided.

      Warning

      All settings of the cluster object you are modifying will be reset to their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the updateMask parameter.

    • maintenanceWindow: Maintenance window settings, applying to both running and stopped clusters. In maintenanceWindow, provide one of these two parameters:

      • anytime: Maintenance can take place at any time.

      • weeklyMaintenanceWindow: Maintenance takes place once a week at the specified time:

        • day: Day of week in DDD format, i.e., MON, TUE, WED, THU, FRI, SAT, or SUN.

        • hour: UTC hour interval, from 1 to 24.

          For example, 1 stands for the interval from 00:00 to 01:00, and 5, from 04:00 to 05:00.

  3. Check the server response to make sure your request was successful.

  1. Get an IAM token for API authentication and put it into an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume that the repository contents reside in the ~/cloudapi/ directory.

  3. Call the ClusterService.Update method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/metastore/v1/cluster_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
           "cluster_id": "<cluster_ID>",
           "update_mask": {
             "paths": [
               "maintenance_window"
             ]
           },
           "maintenance_window": {
             "weekly_maintenance_window": {
               "day": "<day_of_week>",
               "hour": "<sequence_number_of_hour_interval>"
             }
           }
         }' \
      metastore.api.cloud.yandex.net:443 \
      yandex.cloud.metastore.v1.ClusterService.Update \
    

    Where:

    • cluster_id: Cluster ID which you can get with the list of clusters in the folder.

    • update_mask: List of settings to update as an array of strings (paths[]).

      Format for listing settings
      "update_mask": {
        "paths": [
          "<setting_1>",
          "<setting_2>",
          ...
          "<setting_N>"
        ]
      }
      

      In this example, only the maintenance_window setting is provided.

      Warning

      All settings of the cluster object you are modifying will be reset to their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the update_mask parameter.

    • maintenance_window: Maintenance window settings, applying to both running and stopped clusters. In maintenance_window, provide one of these two parameters:

      • anytime: Maintenance can take place at any time.

      • weekly_maintenance_window: Maintenance takes place once a week at the specified time:

        • day: Day of week in DDD format, i.e., MON, TUE, WED, THU, FRI, SAT, or SUN.

        • hour: UTC hour interval, from 1 to 24.

          For example, 1 stands for the interval from 00:00 to 01:00, and 5, from 04:00 to 05:00.

  4. Check the server response to make sure your request was successful.

Apache® and Apache Hive™ are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries.

Was the article helpful?

Previous
Managing cluster access
Next
Deleting a cluster
© 2026 Direct Cursus Technology L.L.C.