Static Group Move
Article under development
Tip
New YDB clusters are recommended to be deployed using configuration V2. If a cluster was deployed using configuration V1, it will still use it after updating to YDB version 25.1 or higher. After such an update, it is recommended to plan and perform migration to V2, because support for V1 will be discontinued in future versions of YDB. For the instructions on how to determine the configuration version of the cluster, see Checking Configuration Version.
When using Configuration V2, static group management is performed automatically and the Self Heal mechanism will perform reconfiguration when one static group node fails.
When manual static group configuration management is needed, you need to disable automatic static group management, get the current static group configuration, make changes and apply the modified configuration as the target static group configuration. Then you need to remove the target static group configuration from the configuration file and enable automatic static group configuration management.
Warning
Incorrect sequence of actions or configuration errors can lead to YDB cluster unavailability.
As an example, consider a YDB cluster where a static node is configured and running on the host with node_id:1
. This node serves part of the static group.
Static group configuration fragment:
...
groups:
...
rings:
...
fail_domains:
- vdisk_locations:
- node_id: 1
path: /dev/vda
pdisk_category: SSD
...
...
To replace node_id:1
, we use another host with a static node deployed on it with node_id:10
.
To move part of the static group from host node_id:1
to node_id:10
:
-
Disable automatic static group management.
-
Get the current static group configuration.
-
Make changes and apply the modified configuration as the target static group configuration.
In the configuration fileconfig.yaml
, change thenode_id
value, replacing the identifier of the host being removed with the identifier of the host being added:... groups: ... rings: ... fail_domains: - vdisk_locations: - node_id: 10 path: /dev/vda pdisk_category: SSD ... ...
Change the
path
and diskpdisk_category
if they differ on the host withnode_id: 10
. -
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.
-
Remove the target static group configuration from the configuration file and enable automatic static group configuration management.