Discuss with expertTry it for free
© 2026 Direct Cursus Technology L.L.C.

Yandex StoreDoc cluster maintenance

Written by
Updated at November 12, 2026
View in Markdown

You can manage maintenance of a Yandex StoreDoc cluster.

Getting a list of maintenance jobs

For Yandex StoreDoc, you can get a list of maintenance jobs in a cloud, folder, or cluster.

Getting a list of maintenance jobs in a cloud

  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 POST \
--header "Authorization: Bearer $IAM_TOKEN" \
--header "Content-Type: application/json" \
--url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/maintenances' \
--data '{
            "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/mongodb/v1/maintenance_service.proto \
  -rpc-header "Authorization: Bearer $IAM_TOKEN" \
  -d '{
        "cloud_id": "<cloud_ID>"
      }' \
  mdb.api.cloud.yandex.net:443 \
  yandex.cloud.mdb.mongodb.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 folder

  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 POST \
--header "Authorization: Bearer $IAM_TOKEN" \
--header "Content-Type: application/json" \
--url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/maintenances' \
--data '{
            "folderId": "<folder_ID>"
        }'

    Learn how to get a folder 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/mongodb/v1/maintenance_service.proto \
  -rpc-header "Authorization: Bearer $IAM_TOKEN" \
  -d '{
        "folder_id": "<folder_ID>"
      }' \
  mdb.api.cloud.yandex.net:443 \
  yandex.cloud.mdb.mongodb.v1.MaintenanceService.List

    Learn how to get a folder ID in this guide.

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

Getting a list of maintenance jobs in a cluster

  1. Navigate to Yandex StoreDoc.
  2. Click the name of your cluster and select the Maintenance tab.

To view maintenance jobs with a specific status, click Status above the list of maintenance jobs and select the status you want from the drop-down menu. You can also find a maintenance job by its ID or name using the search field above the list.

Click an ID to see how the maintenance job affects cluster availability. Look up Task details to see how the maintenance job affects users.

  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 POST \
--header "Authorization: Bearer $IAM_TOKEN" \
--header "Content-Type: application/json" \
--url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/maintenances' \
--data '{
            "resourceId": "<cluster_ID>"
        }'

    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 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/mongodb/v1/maintenance_service.proto \
  -rpc-header "Authorization: Bearer $IAM_TOKEN" \
  -d '{
        "resource_id": "<cluster_ID>"
      }' \
  mdb.api.cloud.yandex.net:443 \
  yandex.cloud.mdb.mongodb.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 details

  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 POST \
--header "Authorization: Bearer $IAM_TOKEN" \
--header "Content-Type: application/json" \
--url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/maintenances/<maintenance_job_ID>'

    You can request the maintenance job ID along with the list of maintenance jobs in a cloud, folder, or cluster.

  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/mongodb/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.mongodb.v1.MaintenanceService.Get

    You can request the maintenance job ID along with the list of maintenance jobs in a cloud, folder, or cluster.

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

Getting maintenance-related cluster logs

  1. Navigate to Yandex StoreDoc.
  2. Click the name of your cluster and select the Maintenance tab.
  3. Click the ID of the maintenance job you need.
  4. Click Task logs.

Postpone the planned maintenance

Maintenance jobs with the Planned status have a specific scheduled date and time specified in the Start date column. You can reschedule them to a new date and time if needed.

To reschedule maintenance for a new date and time:

  1. Navigate to Yandex StoreDoc.
  2. Click the name of your cluster and select the Maintenance tab.
  3. Click next to the maintenance job with the Planned status.
  4. In the drop-down menu, select Postpone.
  5. In the window that opens:
    • To postpone the maintenance until the next available window, click Next window and then Reschedule.
    • To reschedule maintenance to a specific UTC date and time, click Choose date (UTC), then select a new date and time interval and 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 reschedule maintenance for a new date and time:

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

    yc managed-mongodb cluster reschedule-maintenance --help

  2. To reschedule to the next available window, run this command using the next-available-window reschedule type. To reschedule to a specific date and time, use the specific-time reschedule type:

    yc managed-mongodb cluster reschedule-maintenance <cluster_name_or_ID> \
   --reschedule-type <reschedule_type> \
   --delayed-until <timestamp>

    Where:

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

    • --reschedule-type: Rescheduling type. Its possible values are:

      • next-available-window: Postpone maintenance until the next available window.
      • specific-time: Reschedule maintenance for a new date and time.

    • --delayed-until: Timestamp for the specific-time type.

      The timestamp may be in one of the following formats:

      • RFC-3339.
      • HH:MM:SS.
      • Maintenance time offset in hours and minutes.

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

To reschedule maintenance for a new date and time:

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

    export IAM_TOKEN="<IAM_token>"

  2. Transfer your maintenance job using one of these two methods:

    • 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-mongodb/v1/clusters/<cluster_ID>:rescheduleMaintenance' \
--data '{
            "rescheduleType": <reschedule_type>,
            "delayedUntil": <timestamp>
        }'

      Where:

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

      • rescheduleType: Rescheduling type. Its possible values are:

        • NEXT_AVAILABLE_WINDOW: Postpone maintenance until the next available window.
        • SPECIFIC_TIME: Reschedule maintenance for a new date and time.

      • delayedUntil: Timestamp for the SPECIFIC_TIME type in RFC-3339 format.

        Example: 2006-01-02T15:04:05Z.

    • 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-mongodb/v1/maintenances/<maintenance_job_ID>:reschedule' \
--data '{
            "rescheduleType": <reschedule_type>,
            "scheduledAt": <timestamp>
        }'

      Where:

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

      • rescheduleType: Rescheduling type. Its possible values are:

        • NEXT_AVAILABLE_WINDOW: Postpone maintenance until the next available window.
        • SPECIFIC_TIME: Reschedule maintenance for a new date and time.

      • scheduledAt: Timestamp for the SPECIFIC_TIME type in RFC-3339 format.

        Example: 2006-01-02T15:04:05Z.

  3. Make sure the request was successful by examining the server response for the Cluster.RescheduleMaintenance or Maintenance.Reschedule method.

  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. Transfer your maintenance job using one of these two methods:

    • 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/mongodb/v1/cluster_service.proto \
  -rpc-header "Authorization: Bearer $IAM_TOKEN" \
  -d '{
        "cluster_id": "<cluster_ID>",
        "reschedule_type": <reschedule_type>,
        "delayed_until": <timestamp>
      }' \
  mdb.api.cloud.yandex.net:443 \
  yandex.cloud.mdb.mongodb.v1.ClusterService.RescheduleMaintenance

      Where:

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

      • reschedule_type: Rescheduling type. Its possible values are:

        • NEXT_AVAILABLE_WINDOW: Postpone maintenance until the next available window.
        • SPECIFIC_TIME: Reschedule maintenance for a new date and time.

      • delayed_until: Timestamp for the SPECIFIC_TIME type in RFC-3339 format.

        Example: 2006-01-02T15:04:05Z.

    • 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/mongodb/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.mongodb.v1.MaintenanceService.Reschedule

      Where:

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

      • reschedule_type: Rescheduling type. Its possible values are:

        • NEXT_AVAILABLE_WINDOW: Postpone maintenance until the next available window.
        • SPECIFIC_TIME: Reschedule maintenance for a new date and time.

      • scheduled_at: Timestamp for the SPECIFIC_TIME type in RFC-3339 format.

        Example: 2006-01-02T15:04:05Z.

  4. Make sure the request was successful by examining the server response for the ClusterService.Reschedule or MaintenanceService.Reschedule method.

Starting scheduled maintenance immediately

If necessary, you can run a maintenance job with the Planned status immediately, prior to the time specified in the Start date column.

To run a scheduled cluster maintenance job immediately:

  1. Navigate to Yandex StoreDoc.
  2. Click the name of your cluster and select the Maintenance tab.
  3. Click next to the maintenance job you need.
  4. In the drop-down menu, 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 run a scheduled cluster maintenance job immediately:

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

    yc managed-mongodb cluster reschedule-maintenance --help

  2. Run this command using the immediate reschedule type:

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

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

To run a scheduled cluster maintenance job immediately:

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

    export IAM_TOKEN="<IAM_token>"

  2. Perform your maintenance job using one of these two methods:

    • 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-mongodb/v1/clusters/<cluster_ID>:rescheduleMaintenance' \
--data '{
            "rescheduleType": "IMMEDIATE"
        }'

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

    • 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-mongodb/v1/maintenances/<maintenance_job_ID>:reschedule' \
--data '{
            "rescheduleType": "IMMEDIATE"
        }'

      You can request the maintenance job ID along with the list of maintenance jobs in a cloud, folder, or cluster.

  3. Make sure the request was successful by examining the server response for the Cluster.RescheduleMaintenance or Maintenance.Reschedule method.

  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. Perform your maintenance job using one of these two methods:

    • 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/mongodb/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.mongodb.v1.ClusterService.RescheduleMaintenance

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

    • 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/mongodb/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.mongodb.v1.MaintenanceService.Reschedule

      You can request the maintenance job ID along with the list of maintenance jobs in a cloud, folder, or cluster.

  4. Make sure the request was successful by examining the server response for the ClusterService.Reschedule or MaintenanceService.Reschedule method.

Configuring a maintenance window

By default, maintenance can be scheduled for any time. You can choose a specific day of week and hour interval for the start of the maintenance. For example, you can specify the least busy time interval for the cluster.

  1. Navigate to Yandex StoreDoc.
  2. Click the name of your cluster and select the Maintenance tab.
  3. Click Configure the maintenance window.
  4. In the window that opens:
    • To allow maintenance at any time, select At any time, which is also the default option.
    • To allow weekly maintenance at a specific time, select By schedule and specify the day of the week and UTC time interval.

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.

  1. See the description of the CLI command for updating the maintenance window:

    yc managed-mongodb cluster update --help

  2. Run this command:

    yc managed-mongodb 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 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 StoreDoc cluster fields, see this Terraform provider guide.

  2. To set up the maintenance window that will also apply to stopped clusters, add the maintenance_window section to the cluster description:

    resource "yandex_mdb_mongodb_cluster" "<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: Sequence number of 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.

    Timeouts

    The Terraform provider sets the following timeouts for Yandex StoreDoc cluster operations:

    • Creating a cluster, including by restoring one from a backup: 30 minutes.
    • Editing a cluster: 60 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_mongodb_cluster" "<cluster_name>" {
  ...
  timeouts {
    create = "1h30m" # An hour and a half
    update = "2h"    # Two hours
  }
}

  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:

    Warning

    The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the updateMask parameter as a single comma-separated string.

    curl \
  --request PATCH \
  --header "Authorization: Bearer $IAM_TOKEN" \
  --header "Content-Type: application/json" \
  --url 'https://mdb.api.cloud.yandex.net/managed-mongodb/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.

      Here, we provide only one setting.

    • maintenanceWindow: Maintenance window settings, including for stopped clusters. In maintenanceWindow, provide one of these two parameters:

      • anytime: Maintenance can be scheduled for any time.

      • weeklyMaintenanceWindow: Maintenance can only be scheduled for a specific day of week and hour interval:

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

        • hour: UTC hour interval in HH format, 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:

    Warning

    The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the update_mask parameter as an array of paths[] strings.

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

    grpcurl \
  -format json \
  -import-path ~/cloudapi/ \
  -import-path ~/cloudapi/third_party/googleapis/ \
  -proto ~/cloudapi/yandex/cloud/mdb/mongodb/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.mongodb.v1.ClusterService.Update

    Where:

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

      Here, we provide only one setting.

    • maintenance_window: Maintenance window settings, including for stopped clusters. In maintenance_window, provide one of these two parameters:

      • anytime: Maintenance can be scheduled for any time.

      • weekly_maintenance_window: Maintenance can only be scheduled for a specific day of week and hour interval:

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

        • hour: UTC hour interval in HH format, 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.

Previous
Updating cluster settings
Next
Yandex StoreDoc version update