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

# State Storage Move


If you need to decommission a YDB cluster host that contains part of [State Storage](https://ydb.tech/docs/en/reference/configuration/domains_config.md#domains-state), 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 with the following State Storage configuration:

```yaml
...
domains_config:
  ...
  state_storage:
  - ring:
      node: [1, 2, 3, 4, 5, 6, 7, 8, 9]
      nto_select: 9
    ssid: 1
  ...
...
```

On the host with `node_id:1`, a cluster [static node](https://ydb.tech/docs/en/reference/configuration/hosts.md#hosts) is configured and running, which serves part of State Storage. Suppose we need to decommission this host.

To replace `node_id:1`, we [added](https://ydb.tech/docs/en/devops/configuration-management/configuration-v1/cluster-expansion.md#add-host) 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 State Storage from host `node_id:1` to `node_id:10`:

1. Stop the cluster static nodes on hosts with `node_id:1` and `node_id:10`.

    <!-- 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 -->

1. In the configuration file `config.yaml`, change the `node` host list, replacing the identifier of the host being removed with the identifier of the host being added:

    ```yaml
    domains_config:
    ...
      state_storage:
      - ring:
          node: [2, 3, 4, 5, 6, 7, 8, 9, 10]
          nto_select: 9
        ssid: 1
    ...
    ```

1. Update the configuration files `config.yaml` for all cluster nodes, including dynamic ones.
1. Using the [rolling-restart](https://ydb.tech/docs/en/maintenance/manual/node_restarting.md) procedure, restart all cluster nodes, including dynamic ones, except for static nodes on hosts with `node_id:1` and `node_id:10`. Note that a delay of at least 15 seconds is required between host restarts.
1. Start the cluster static nodes on hosts `node_id:1` and `node_id:10`.