We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This command will allow the user to remove a set of permanently lost nodes from a cluster as cleanly as possible to allow the cluster to recover.
Relevant Core PR: #13943
rpk cluster partitions unsafe-recover --from-nodes 1,2,3 [--no-confirm] [--dry][--format]
The idea is to use the Admin API to perform the operation:
We can use GET /v1/debug/force_replicas_from_nodes to get the move plan and display it in our standard table format.
GET /v1/debug/force_replicas_from_nodes
$ rpk cluster partitions unsafe-recover --from-nodes 1,2 NAMESPACE TOPIC PARTITION CURRENT-NODE:REPLICA TARGET-NODE:REPLICAS INFO kafka foo 231 [1:22, 2:11] [3:1, 3:2]
And then prompt the user to confirm and apply the plan.
GET /v1/debug/force_replicas_from_nodes and POST /v1/debug/force_replicas_from_nodes endpoints are being added in #13943
POST /v1/debug/force_replicas_from_nodes
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Who is this for and what problem do they have today?
This command will allow the user to remove a set of permanently lost nodes from a cluster as cleanly as possible to allow the cluster to recover.
Relevant Core PR: #13943
Proposed Command
The idea is to use the Admin API to perform the operation:
We can use
GET /v1/debug/force_replicas_from_nodes
to get the move plan and display it in our standard table format.And then prompt the user to confirm and apply the plan.
Additional notes
GET /v1/debug/force_replicas_from_nodes
andPOST /v1/debug/force_replicas_from_nodes
endpoints are being added in #13943The text was updated successfully, but these errors were encountered: