Cluster Configuration Migration
YDB supports two configuration management mechanisms: V1 and V2 (recommended, available from version 25.1). Key differences between them are described in the article Comparing configurations V1 and V2.
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.
Depending on the current state of your cluster, you can perform migration:
- To configuration V2: If your cluster is running under configuration V1 management (for example, was deployed on YDB version before 25.1 and has been updated to 25.1), you can switch to the configuration V2 mechanism.
- To configuration V1: If unexpected problems arose after switching to configuration V2, or you need to roll back the YDB version below 25.1, you can perform reverse migration to manual configuration management (V1).
Problems during migration?
If unexpected problems arise when using migration instructions (especially when rolling back to V1), it is recommended to report them immediately as a GitHub issue, providing maximum context and diagnostics for reproduction.
Before performing migration, make sure to determine which configuration version is currently used in your cluster using the version check instructions.