rpk topic storage mode-migration retry

Retry the storage mode migration of backed-off partitions.

A partition’s storage mode migration backs off after making no progress for topic_storage_mode_migration_error_backoff_timeout. The partition stays in its previous storage mode, and no more of the topic’s partitions are admitted until it is retried. rpk topic storage mode-migration describe lists these partitions as BACKED-OFF-PARTITIONS.

A retried partition starts its migration over, discarding what it had imported into cloud topics metadata.

Without --partitions, this command retries every partition that the topic reports as backed off. A partition whose leader does not respond is not reported, so it is not retried.

Retrying a partition that has not backed off fails. So does retrying a partition whose leader can’t be reached or that is moving between brokers. Rerun the command later to retry it again.

This command was introduced in version v26.3.1.

Usage

rpk topic storage mode-migration retry TOPIC [flags]

Examples

This section provides examples of how to use rpk topic storage mode-migration retry.

Retry every backed-off partition of a topic:

rpk topic storage mode-migration retry foo

Retry partitions 0 and 3 of a topic:

rpk topic storage mode-migration retry foo -p 0,3

Flags

Value Type Description

--format

string

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

-p, --partitions

int32Slice

Comma-separated list of partitions to retry.

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.