Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.
Yandex MPP Analytics for PostgreSQL
  • Getting started
    • All guides
      • Information about existing clusters
      • Creating a cluster
      • Expanding a cluster
      • Editing the cluster configuration
      • Updating cluster settings
      • Stopping and starting a cluster
      • Managing backups
      • Managing cluster access
      • Yandex MPP Analytics for PostgreSQL version upgrade
      • Maintenance
      • Deleting a cluster
    • Connecting to an external file server (gpfdist)
    • Access from Trino
    • Auxiliary utilities
  • Access management
  • Inspections and recommendations
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Getting a list of maintenance jobs
  • Getting a list of maintenance jobs in a cloud
  • Getting a list of maintenance jobs in a folder
  • Getting a list of maintenance jobs in a cluster
  • Getting maintenance job details
  • Getting cluster maintenance logs
  • Postponing scheduled maintenance
  • Starting scheduled maintenance immediately
  • Configuring a maintenance window
  1. Step-by-step guides
  2. Clusters
  3. Maintenance

Yandex MPP Analytics for PostgreSQL cluster maintenance

Written by
Yandex Cloud
Updated at November 12, 2026
View in Markdown
  • Getting a list of maintenance jobs
    • Getting a list of maintenance jobs in a cloud
    • Getting a list of maintenance jobs in a folder
    • Getting a list of maintenance jobs in a cluster
  • Getting maintenance job details
  • Getting cluster maintenance logs
  • Postponing scheduled maintenance
  • Starting scheduled maintenance immediately
  • Configuring a maintenance window

You can manage maintenance of a Yandex MPP Analytics for PostgreSQL cluster.

Getting a list of maintenance jobsGetting a list of maintenance jobs

For Yandex MPP Analytics for PostgreSQL, you can get a list of maintenance jobs in:

  • Cloud
  • Folder
  • Cluster

Getting a list of maintenance jobs in a cloudGetting a list of maintenance jobs in a cloud

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

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

    curl \
      --request GET \
      --header "Authorization: Bearer $IAM_TOKEN" \
      --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/maintenances?cloudId=<cloud_ID>'
    

    Learn how to get a cloud ID in this guide.

  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 MaintenanceService.List method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/maintenance_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
            "cloud_id": "<cloud_ID>"
          }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.greenplum.v1.MaintenanceService.List
    

    Learn how to get a cloud ID in this guide.

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

Getting a list of maintenance jobs in a folderGetting a list of maintenance jobs in a folder

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

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

    curl \
      --request GET \
      --header "Authorization: Bearer $IAM_TOKEN" \
      --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/maintenances?folderId=<folder_ID>'
    

    You can get the folder ID with the list of folders in the cloud.

  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 MaintenanceService.List method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/maintenance_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
            "folder_id": "<folder_ID>"
          }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.greenplum.v1.MaintenanceService.List
    

    You can get the folder ID with the list of folders in the cloud.

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

Getting a list of maintenance jobs in a clusterGetting a list of maintenance jobs in a cluster

Management console
REST API
gRPC API
  1. Open the folder dashboard.
  2. Navigate to Yandex MPP Analytics for PostgreSQL.
  3. Click the name of your cluster and select the Maintenance tab.
  4. Optionally, select a maintenance status above the list of maintenance jobs.
  1. Get an IAM token for API authentication and put it into an environment variable:

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

    curl \
      --request GET \
      --header "Authorization: Bearer $IAM_TOKEN" \
      --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/maintenances?resourceId=<cluster_ID>'
    

    You can get the cluster ID with the list of clusters in the folder.

  3. View 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 MaintenanceService.List method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/maintenance_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
            "resource_id": "<cluster_ID>"
          }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.greenplum.v1.MaintenanceService.List
    

    You can get the cluster ID with the list of clusters in the folder.

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

Getting maintenance job detailsGetting maintenance job details

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

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

    curl \
      --request GET \
      --header "Authorization: Bearer $IAM_TOKEN" \
      --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/maintenances/<maintenance_job_ID>'
    

    You can get the maintenance job ID with the list of maintenance jobs.

  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 MaintenanceService.Get method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/maintenance_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
            "maintenance_id": "<maintenance_job_ID>"
          }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.greenplum.v1.MaintenanceService.Get
    

    You can get the maintenance job ID with the list of maintenance jobs.

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

Getting cluster maintenance logsGetting cluster maintenance logs

Management console
  1. Open the folder dashboard.
  2. Navigate to Yandex MPP Analytics for PostgreSQL.
  3. Click the name of your cluster and select the Maintenance tab.
  4. Select the maintenance. The maintenance page will open.
  5. Click Task logs.

Postponing scheduled maintenancePostponing scheduled maintenance

Management console
CLI
REST API
gRPC API
  1. Open the folder dashboard.

  2. Navigate to Yandex MPP Analytics for PostgreSQL.

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

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

  5. 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 interval (UTC).

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

      Maintenance can be postponed from its originally scheduled date:

      • By a maximum of two and a half months for major Greenplum® version updates, e.g., from 6.28.20 to 6.29.8.
      • By a maximum of one month for updates between minor Greenplum® versions, e.g., from 6.29.1 to 6.29.2.
      • By a maximum of two weeks for all other types of maintenance.
  6. Click Reschedule.

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 postpone scheduled maintenance:

  1. View the description of the CLI command for rescheduling maintenance:

    yc managed-greenplum cluster reschedule-maintenance --help
    
  2. Reschedule the maintenance:

    yc managed-greenplum cluster reschedule-maintenance <cluster_name_or_ID> \
      --reschedule-type <reschedule_type>
    

    Where reschedule_type is reschedule type:

    • next-available-window: Next available maintenance window.

    • specific-time: Specific date and time, UTC.

      For this value, also use the --delayed-until parameter to provide a timestamp in one of these formats:

      • RFC 3339.
      • HH:MM:SS.
      • Relative time to postpone maintenance for.

      Here are some examples: 2006-01-02T15:04:05Z, 15:04:05, 2h, 3h30m ago.

      Maintenance can be postponed from its originally scheduled date:

      • By a maximum of two and a half months for major Greenplum® version updates, e.g., from 6.28.20 to 6.29.8.
      • By a maximum of one month for updates between minor Greenplum® versions, e.g., from 6.29.1 to 6.29.2.
      • By a maximum of two weeks for all other types of maintenance.

    You can get the cluster name and ID with the list of clusters in the folder.

You can reschedule a scheduled maintenance job using one of these methods:

  • Cluster.RescheduleMaintenance
  • Maintenance.Reschedule

To postpone a scheduled maintenance job using the Cluster.RescheduleMaintenance method:

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

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

    curl \
      --request POST \
      --header "Authorization: Bearer $IAM_TOKEN" \
      --header "Content-Type: application/json" \
      --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/clusters/<cluster_ID>:rescheduleMaintenance' \
      --data '{
               "rescheduleType": "<reschedule_type>"
             }'
    

    Where reschedule_type is reschedule type:

    • NEXT_AVAILABLE_WINDOW: Next available maintenance window.

    • SPECIFIC_TIME: Specific date and time, UTC.

      For this value, also use the delayedUntil parameter to provide a timestamp in RFC 3339 format, e.g., 2006-01-02T15:04:05Z.

      Maintenance can be postponed from its originally scheduled date:

      • By a maximum of two and a half months for major Greenplum® version updates, e.g., from 6.28.20 to 6.29.8.
      • By a maximum of one month for updates between minor Greenplum® versions, e.g., from 6.29.1 to 6.29.2.
      • By a maximum of two weeks for all other types of maintenance.

    You can get the cluster ID with the list of clusters in the folder.

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

To postpone a scheduled maintenance job using the Maintenance.Reschedule method:

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

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

    curl \
      --request POST \
      --header "Authorization: Bearer $IAM_TOKEN" \
      --header "Content-Type: application/json" \
      --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/maintenances/<maintenance_job_ID>:reschedule' \
      --data '{
                "rescheduleType": "<reschedule_type>"
              }'
    

    Where:

    • <maintenance_job_ID>: Maintenance job ID you can get with the list of maintenance jobs.

    • rescheduleType: Reschedule type:

      • NEXT_AVAILABLE_WINDOW: Next available maintenance window.

      • SPECIFIC_TIME: Specific date and time, UTC.

        For this value, also use the scheduledAt parameter to provide a timestamp in RFC 3339 format, e.g., 2006-01-02T15:04:05Z.

        Maintenance can be postponed from its originally scheduled date:

        • By a maximum of two and a half months for major Greenplum® version updates, e.g., from 6.28.20 to 6.29.8.
        • By a maximum of one month for updates between minor Greenplum® versions, e.g., from 6.29.1 to 6.29.2.
        • By a maximum of two weeks for all other types of maintenance.
  3. Check the server response to make sure your request was successful.

You can reschedule a scheduled maintenance job using one of these calls:

  • ClusterService.RescheduleMaintenance
  • MaintenanceService.Reschedule

To postpone a scheduled maintenance job using the ClusterService.RescheduleMaintenance call:

  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.RescheduleMaintenance method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/cluster_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
           "cluster_id": "<cluster_ID>",
           "reschedule_type": "<reschedule_type>"
          }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.greenplum.v1.ClusterService.RescheduleMaintenance
    

    Where reschedule_type is reschedule type:

    • NEXT_AVAILABLE_WINDOW: Next available maintenance window.

    • SPECIFIC_TIME: Specific date and time, UTC.

      For this value, also use the delayed_until parameter to provide a timestamp in RFC 3339 format, e.g., 2006-01-02T15:04:05Z.

      Maintenance can be postponed from its originally scheduled date:

      • By a maximum of two and a half months for major Greenplum® version updates, e.g., from 6.28.20 to 6.29.8.
      • By a maximum of one month for updates between minor Greenplum® versions, e.g., from 6.29.1 to 6.29.2.
      • By a maximum of two weeks for all other types of maintenance.

    You can get the cluster ID with the list of clusters in the folder.

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

To postpone a scheduled maintenance job using the MaintenanceService.Reschedule call:

  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 MaintenanceService.Reschedule method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/maintenance_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
            "maintenance_id": "<maintenance_job_ID>",
            "reschedule_type": "<reschedule_type>",
            "scheduled_at": "<timestamp>"
          }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.greenplum.v1.MaintenanceService.Reschedule
    

    Where:

    • maintenance_id: Maintenance job ID you can get with the list of maintenance jobs.

    • reschedule_type: Reschedule type:

      • NEXT_AVAILABLE_WINDOW: Next available maintenance window.

      • SPECIFIC_TIME: Specific date and time, UTC.

        For this value, also use the scheduled_at parameter to provide a timestamp in RFC 3339 format, e.g., 2006-01-02T15:04:05Z.

        Maintenance can be postponed from its originally scheduled date:

        • By a maximum of two and a half months for major Greenplum® version updates, e.g., from 6.28.20 to 6.29.8.
        • By a maximum of one month for updates between minor Greenplum® versions, e.g., from 6.29.1 to 6.29.2.
        • By a maximum of two weeks for all other types of maintenance.
  4. Check the server response to make sure your request was successful.

Starting scheduled maintenance immediatelyStarting scheduled maintenance immediately

Management console
CLI
REST API
gRPC API
  1. Open the folder dashboard.
  2. Navigate to Yandex MPP Analytics for PostgreSQL.
  3. Click the name of your cluster and select the Maintenance tab.
  4. In the maintenance row, click and select Carry out now.

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 start scheduled maintenance immediately, do the following:

  1. View the description of the CLI command for rescheduling maintenance:

    yc managed-greenplum cluster reschedule-maintenance --help
    
  2. Start scheduled maintenance immediately:

    yc managed-greenplum cluster reschedule-maintenance <cluster_name_or_ID> \
      --reschedule-type immediate
    

    You can get the cluster name and ID with the list of clusters in the folder.

You can run a scheduled maintenance job immediately using one of these methods:

  • Cluster.RescheduleMaintenance
  • Maintenance.Reschedule

To run a scheduled maintenance job immediately using the Cluster.RescheduleMaintenance method:

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

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

    curl \
      --request POST \
      --header "Authorization: Bearer $IAM_TOKEN" \
      --header "Content-Type: application/json" \
      --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/clusters/<cluster_ID>:rescheduleMaintenance' \
      --data '{
               "rescheduleType": "IMMEDIATE"
             }'
    

    You can get the cluster ID with the list of clusters in the folder.

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

To run a scheduled maintenance job immediately using the Maintenance.Reschedule method:

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

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

    curl \
      --request POST \
      --header "Authorization: Bearer $IAM_TOKEN" \
      --header "Content-Type: application/json" \
      --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/maintenances/<maintenance_job_ID>:reschedule' \
      --data '{
                "rescheduleType": "IMMEDIATE"
              }'
    

    You can get the maintenance job ID with the list of maintenance jobs.

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

You can run a scheduled maintenance job immediately using one of these calls:

  • ClusterService.RescheduleMaintenance
  • MaintenanceService.Reschedule

To run a scheduled maintenance job immediately using the ClusterService.RescheduleMaintenance call:

  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.RescheduleMaintenance method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/cluster_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
           "cluster_id": "<cluster_ID>",
           "reschedule_type": "IMMEDIATE"
         }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.greenplum.v1.ClusterService.RescheduleMaintenance
    

    You can get the cluster ID with the list of clusters in the folder.

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

To run a scheduled maintenance job immediately using the MaintenanceService.Reschedule call:

  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 MaintenanceService.Reschedule method, e.g., via the following gRPCurl request:

    grpcurl \
      -format json \
      -import-path ~/cloudapi/ \
      -import-path ~/cloudapi/third_party/googleapis/ \
      -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/maintenance_service.proto \
      -rpc-header "Authorization: Bearer $IAM_TOKEN" \
      -d '{
            "maintenance_id": "<maintenance_job_ID>",
            "reschedule_type": "IMMEDIATE"
          }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.greenplum.v1.MaintenanceService.Reschedule
    

    You can get the maintenance job ID with the list of maintenance jobs.

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

Configuring a maintenance windowConfiguring a maintenance window

Management console
CLI
Terraform
REST API
gRPC API
  1. Open the folder dashboard.

  2. Navigate to Yandex MPP Analytics for PostgreSQL.

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

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

  5. Select a maintenance window:

    • At any time: Maintenance takes place at any time.

    • By schedule: Maintenance is scheduled for the selected day of the week and UTC time interval.

      For this type of maintenance, define the start of the maintenance window: select the day of the week and UTC time interval.

  6. 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 set a maintenance window:

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

    yc managed-greenplum cluster update --help
    
  2. Set up a maintenance window:

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

    Where type is 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: 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.

    You can get the cluster name and ID with the list of clusters in the folder.

  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 Yandex MPP Analytics for PostgreSQL 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_mdb_greenplum_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 (default).
      • 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 intended 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.

    Warning

    The Terraform provider limits the amount of time for all Yandex MPP Analytics for PostgreSQL cluster operations to complete to 120 minutes.

    Operations exceeding the set timeout are interrupted.

    How do I change these limits?

    Add the timeouts block to the cluster description, for example:

    resource "yandex_mdb_greenplum_cluster" "<cluster name>" {
      ...
      timeouts {
        create = "1h30m" # 1 hour 30 minutes
        update = "2h"    # 2 hours
        delete = "30m"   # 30 minutes
      }
    }
    
  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://mdb.api.cloud.yandex.net/managed-greenplum/v1/clusters/<cluster_ID>' \
      --data '{
               "updateMask": "maintenanceWindow",
               "maintenanceWindow": {
                 "weeklyMaintenanceWindow": {
                   "day": "<day_of_week>",
                   "hour": "<sequence_number_of_hour_interval>"
                 }
               }
             }'
    

    Where:

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

      In this example, only the maintenanceWindow setting is provided.

      Warning

      When you update a cluster, all parameters of the 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. Provide one of these parameters:

      • anytime: Allows performing maintenance at any time; default option.

        This parameter is provided as an empty object: "anytime": {}.

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

        • day: Day of week, 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.

    You can get the cluster ID with the list of clusters in the folder.

  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/mdb/greenplum/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>"
             }
           }
         }' \
      mdb.api.cloud.yandex.net:443 \
      yandex.cloud.mdb.greenplum.v1.ClusterService.Update
    

    Where:

    • 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

      When you update a cluster, all parameters of the 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. Provide one of these parameters:

      • anytime: Allows performing maintenance at any time; default option.

        This parameter is provided as an empty object: "anytime": {}.

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

        • day: Day of week, 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.

    You can get the cluster ID with the list of clusters in the folder.

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

Was the article helpful?

Previous
Yandex MPP Analytics for PostgreSQL version upgrade
Next
Deleting a cluster
© 2026 Direct Cursus Technology L.L.C.