rpk cluster fencing disable

Disable fencing of the cluster.

After you disable fencing, the cluster accepts writes, changes, and fetches again. The saved settings stay, and rpk cluster fencing enable uses them the next time.

If you failed over a Shadow Link, make sure that your clients use the shadow cluster before you disable fencing on the source cluster.

Use --wait to wait until the cluster reaches the UNFENCED state, which means that every broker stopped fencing.

This command was introduced in version v26.3.1.

Usage

rpk cluster fencing disable [flags]

Examples

This section provides examples of how to use rpk cluster fencing disable.

Disable fencing and wait until every broker stops it:

rpk cluster fencing disable --wait

Disable fencing only if nobody changed it since revision 5:

rpk cluster fencing disable --expected-revision 5

Flags

Value Type Description

--expected-revision

int64

Fail if fencing is not at this revision, as rpk cluster fencing status reports it.

--format

string

Output format (json,yaml,text,wide,help). Default: text.

--no-confirm

bool

Disable confirmation prompt.

-w, --wait

bool

Wait until the cluster reaches the UNFENCED state.

Global flags

Value Type Description

--config

string

Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml.

-X, --config-opt

stringArray

Override rpk configuration settings; -X help for detail or -X list for terser detail.

--ignore-profile

bool

Ignore rpk.yaml and redpanda.yaml; use default settings.

--profile

string

rpk profile to use.

-v, --verbose

bool

Enable verbose logging.