-
Notifications
You must be signed in to change notification settings - Fork 580
New issue
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
rpk: add transfer-leadership command #18026
rpk: add transfer-leadership command #18026
Conversation
new failures in https://buildkite.com/redpanda/redpanda/builds/48171#018f0b9f-17b5-4007-9596-32a27c1f26d1:
new failures in https://buildkite.com/redpanda/redpanda/builds/48171#018f0ba6-6b52-4814-a0a6-58db8767d3ca:
new failures in https://buildkite.com/redpanda/redpanda/builds/48204#018f0f29-922e-4b1f-a749-e757ca527282:
new failures in https://buildkite.com/redpanda/redpanda/builds/48204#018f0f53-d66e-44d3-9f6d-97d9f7cf1b4d:
new failures in https://buildkite.com/redpanda/redpanda/builds/48621#018f3a1c-e49f-4ef8-a13d-f42b117c3fe2:
new failures in https://buildkite.com/redpanda/redpanda/builds/48805#018f5632-48c8-40a0-8314-ff633b15366d:
new failures in https://buildkite.com/redpanda/redpanda/builds/48805#018f5632-48cb-4f30-9bfe-7502eedf3233:
new failures in https://buildkite.com/redpanda/redpanda/builds/48805#018f563b-1a0e-40f0-8871-c00e20b7f53f:
new failures in https://buildkite.com/redpanda/redpanda/builds/48805#018f563b-1a0c-4d58-ad9f-512b1a8cd295:
|
08bd248
to
6876c82
Compare
Revised the help text a bit. |
6876c82
to
6cf90ff
Compare
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/48204#018f0f29-9229-4fed-803d-a92d42c5ac84 |
Thanks for the PR, to understand: how often is the case where we want to move multiple partitions simultaneously? is the normal scenario running this request multiple times in a row, or is it often just 1~2 leadership transfers? My question is because I see that we have the flexibility, but I don't want the flexibility to become a complex command. If this is a command that it's likely to be a "one-of", something like:
But if it's something that usually comes in multiples, I like your:
And make this the only way to do it, even for 1 movement:
That way our users only have to "learn" one command syntax and it's easier to migrate if the command grows in the future. What do you think @daisukebe @twmb |
Thanks for the question, @r-vasquez. Let me discuss with the field team and get back to you. |
Discussed with the support team and confirmed we rarely transfer multiple partition leaderships at a time these days. Some want multiple but so far we prefer less error-prone. That is, I will update the command to accept only one partition at a time. Syntax-wise, I kinda feel using |
You are right, yes, let's keep it to be consistent with the |
6cf90ff
to
7513815
Compare
7513815
to
eaff6f7
Compare
Allowed to transfer one partition leadership at a time |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see suggested updates for the description.
1a116f4
to
bf7df49
Compare
Thanks @Feediver1! Committed all suggestions and rebased. |
bf7df49
to
a8359e5
Compare
/backport v24.1.x |
/backport v23.3.x |
Fixes #17418
In this implementation, I decided to make the functionality simple for a start. In #17418, I reckoned to support
--partition
and--from
options, but only--partition
flag is supported at this moment.Here's the help text:
Backports Required
Release Notes
Features