---
metadata:
  - name: generator
    content: Diplodoc Platform v5.52.0
alternate:
  - https://ydb.tech/docs/en/reference/ydb-cli/commands/bridge/takedown.md?version=v25.4
  - https://ydb.tech/docs/ru/reference/ydb-cli/commands/bridge/takedown.md?version=v25.4
  - href: en/reference/ydb-cli/commands/bridge/takedown.md
    type: text/markdown
    title: Markdown version
  - href: ../../../../llms.txt
    type: text/markdown
    title: llms.txt
sourcePath: en/core/reference/ydb-cli/commands/bridge/takedown.md
---
> **Documentation Index:** Fetch the complete configuration index at https://ydb.tech/docs/en/llms.txt

# admin cluster bridge takedown

<!-- source: en/_includes/feature_enterprise.md -->
{% note info "Feature of Yandex Enterprise Database" %}

This functionality is available only in the [Yandex Enterprise Database](https://ydb.tech/docs/en/downloads/yandex-enterprise-database.md?version=v25.4). In the open-source version of YDB it is absent.

{% endnote %}
<!-- endsource: en/_includes/feature_enterprise.md -->

Use the `admin cluster bridge takedown` command to perform [planned disable](https://ydb.tech/docs/en/concepts/bridge.md?version=v25.4#takedown) of a pile. If you are disabling the current `PRIMARY`, you must specify the new `PRIMARY`.

<!-- source: en/reference/ydb-cli/commands/_includes/danger-warning.md -->
{% note 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.

{% endnote %}
<!-- endsource: en/reference/ydb-cli/commands/_includes/danger-warning.md -->

General command syntax:

```bash
ydb [global options...] admin cluster bridge takedown [options...]
```

* `global options` — global parameters.
* `options` — [subcommand parameters](#options).

View command help:

```bash
ydb admin cluster bridge takedown --help
```

## Subcommand parameters {#options}

#|
|| Name | Description ||
|| `--pile <pile>` | Name of the pile to take out of the cluster. ||
|| `--new-primary <pile>` | Name of the pile that should become the new `PRIMARY` if the current `PRIMARY` is being disabled. ||
|#

## Requirements {#requirements}

- If you are disabling the current `PRIMARY`, you must specify `--new-primary` and choose a pile in the `SYNCHRONIZED` state.

## Examples {#examples}

Take `SYNCHRONIZED` pile `pile-b` out of the cluster:

```bash
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`:

```bash
ydb admin cluster bridge takedown --pile pile-a --new-primary pile-b
```

### Verifying the result {#verify}

Verify the resulting pile states with the [list](https://ydb.tech/docs/en/reference/ydb-cli/commands/bridge/list.md?version=v25.4) command:

```bash
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`:

```bash
ydb admin cluster bridge list

pile-a: DISCONNECTED
pile-b: PRIMARY
```