admin cluster bridge takedown
Feature of Yandex Enterprise Database
This functionality is available only in the Yandex Enterprise Database. In the open-source version of YDB it is absent.
Use the admin cluster bridge takedown command to perform planned disable of a pile. If you are disabling the current PRIMARY, you must specify the new PRIMARY.
Alert
Commands in this section can harm your cluster if used incorrectly. Due to the potentially dangerous nature of these commands, ALL global parameters must be specified explicitly. Profiles are disabled by default and are only used when explicitly specified (--profile <profile-name>). Some commands do not require global options that are otherwise mandatory.
General command syntax:
ydb [global options...] admin cluster bridge takedown [options...]
global options— global parameters.options— subcommand parameters.
View command help:
ydb admin cluster bridge takedown --help
Subcommand parameters
|
Name |
Description |
|
|
Name of the pile to take out of the cluster. |
|
|
Name of the pile that should become the new |
Requirements
- If you are disabling the current
PRIMARY, you must specify--new-primaryand choose a pile in theSYNCHRONIZEDstate.
Examples
Take SYNCHRONIZED pile pile-b out of the cluster:
ydb admin cluster bridge takedown --pile pile-b
Take PRIMARY pile pile-a out of the cluster and transition pile-b from SYNCHRONIZED to PRIMARY:
ydb admin cluster bridge takedown --pile pile-a --new-primary pile-b
Verifying the result
Verify the resulting pile states with the list command:
ydb admin cluster bridge list
pile-a: PRIMARY
pile-b: DISCONNECTED
If you disabled the current PRIMARY with --new-primary, verify that the chosen pile has become PRIMARY:
ydb admin cluster bridge list
pile-a: DISCONNECTED
pile-b: PRIMARY