---
metadata:
  - name: generator
    content: Diplodoc Platform v5.50.4
alternate:
  - https://ydb.tech/docs/en/devops/configuration-management/configuration-v1/static-group-move.md
  - https://ydb.tech/docs/ru/devops/configuration-management/configuration-v1/static-group-move.md
sourcePath: en/core/devops/configuration-management/configuration-v1/static-group-move.md
---
> **Documentation Index:** Fetch the complete configuration index at https://ydb.tech/docs/en/llms.txt

# Static Group Move

If you need to decommission a YDB cluster host that contains part of the [static group](https://ydb.tech/docs/en/reference/configuration/blob_storage_config.md#blob_storage_config), you need to move it to another host.

<!-- source: en/devops/configuration-management/configuration-v1/_includes/warning-configuration-error.md -->
{% note warning %}

Incorrect sequence of actions or configuration errors can lead to YDB cluster unavailability.

{% endnote %}
<!-- endsource: en/devops/configuration-management/configuration-v1/_includes/warning-configuration-error.md -->

As an example, consider a YDB cluster where a [static node](https://ydb.tech/docs/en/reference/configuration/hosts.md#hosts) is configured and running on the host with `node_id:1`. This node serves part of the static group.

Static group configuration fragment:

```yaml
...
blob_storage_config:
  ...
  service_set:
    ...
    groups:
      ...
      rings:
        ...
        fail_domains:
        - vdisk_locations:
          - node_id: 1
            path: /dev/vda
            pdisk_category: SSD
        ...
      ...
    ...
  ...
...
```

To replace `node_id:1`, we [added](https://ydb.tech/docs/en/devops/configuration-management/configuration-v1/cluster-expansion.md#add-static-node) a new host with `node_id:10` to the cluster and [deployed](https://ydb.tech/docs/en/devops/configuration-management/configuration-v1/cluster-expansion.md#add-static-node) a static node on it.

To move part of the static group from host `node_id:1` to `node_id:10`:

1. Stop the cluster static node on the host with `node_id:1`.

    <!-- source: en/devops/configuration-management/configuration-v1/_includes/fault-tolerance.md -->
    {% note info %}

    A YDB cluster is fault-tolerant. Temporary node shutdown does not lead to cluster unavailability. For more details, see [YDB Cluster Topology](https://ydb.tech/docs/en/concepts/topology.md).

    {% endnote %}
    <!-- endsource: en/devops/configuration-management/configuration-v1/_includes/fault-tolerance.md -->

2. In the configuration file `config.yaml`, change the `node_id` value, replacing the identifier of the host being removed with the identifier of the host being added:

    ```yaml
    ...
    blob_storage_config:
      ...
      service_set:
        ...
        groups:
          ...
          rings:
            ...
            fail_domains:
            - vdisk_locations:
              - node_id: 10
                path: /dev/vda
                pdisk_category: SSD
            ...
          ...
        ...
      ...
    ...
    ```

    Change the `path` and disk `pdisk_category` if they differ on the host with `node_id: 10`.

3. Update the configuration files `config.yaml` for all cluster nodes, including dynamic ones.
4. Using the [rolling-restart](https://ydb.tech/docs/en/maintenance/manual/node_restarting.md) procedure, restart all static cluster nodes.
5. Go to the Embedded UI monitoring page and ensure that the static group VDisk appeared on the target physical disk and is replicating. For more details, see [Monitoring static groups](https://ydb.tech/docs/en/reference/embedded-ui/ydb-monitoring.md#static-group).
6. Using the [rolling-restart](https://ydb.tech/docs/en/maintenance/manual/node_restarting.md) procedure, restart all dynamic cluster nodes.