Skip to content
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

Fixed finishing recommissioning update #7533

Merged
merged 3 commits into from
Nov 29, 2022

Conversation

mmaslankaprv
Copy link
Member

@mmaslankaprv mmaslankaprv commented Nov 28, 2022

c/members_backend: allow empty recommissioning updates to finish

Fixed stop condition to allow recommissioning operations that do not
require reallocations to finish. Previously the recommissioning
operation would only finish if there were reallocations finished. Fixed
the incorrect stop condition by finishing the recommission operation
that does not require reallocations.

Fixes: #7526

Backports Required

  • none - not a bug fix
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v22.3.x
  • v22.2.x
  • v22.1.x

UX Changes

Release Notes

Bug Fixes

  • Fix recommissioning stop condition that might prevent the recommission operation from finishing

Signed-off-by: Michal Maslanka <michal@redpanda.com>
@mmaslankaprv mmaslankaprv changed the title Fix 7526 Fixed finishing recommissioning update Nov 28, 2022
@piyushredpanda piyushredpanda added this to the v22.3.5 milestone Nov 28, 2022
Fixed stop condition to allow recommissioning operations that do not
require reallocations to finish. Previously the recommissioning
operation would only finish if there were reallocations finished. Fixed
the incorrect stop condition by finishing the recommission operation
that does not require reallocations.

Fixes: redpanda-data#7275

Signed-off-by: Michal Maslanka <michal@redpanda.com>
Added test validating that the cycle of
decommission/recommission/decommission of a node is possible.

Signed-off-by: Michal Maslanka <michal@redpanda.com>
Copy link
Contributor

@bharathv bharathv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense to me.

@emaxerrno
Copy link
Contributor

@mmaslankaprv does it make sense to expose an admin api to get this unstuck in the future. something like, node force recomission, discard intermediary state kinda thing?

@mmaslankaprv
Copy link
Member Author

@mmaslankaprv does it make sense to expose an admin api to get this unstuck in the future. something like, node force recomission, discard intermediary state kinda thing?

I will add an admin API that will allow us to force cancel ongoing re-balancing operation in a follow up PR

@mmaslankaprv mmaslankaprv merged commit 5e37ccc into redpanda-data:dev Nov 29, 2022
@piyushredpanda
Copy link
Contributor

@mmaslankaprv please don't forget the backports (and sorry if I missed seeing them)

@mmaslankaprv
Copy link
Member Author

/backport v22.2.x

@mmaslankaprv
Copy link
Member Author

/backport v22.3.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

decommissioning isn't started
4 participants