-
Notifications
You must be signed in to change notification settings - Fork 573
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
Admin API endpoints for forcefully aborting partition movements on cluster/node #5782
Comments
This can be closed/duped, @ztlpn ? |
@piyushredpanda actually no, we have the safe cancellation variants, but forceful abort variants haven't been implemented |
I see, can we link this to a relevant epic, @ztlpn / @mmedenjak ? Perhaps every project should have a epic of must-haves and then later an epic of fast-follows/good-to-haves that inevitably either show up too late for release or get pushed out from the release but stuff we really should be spending time on. |
Do we really need a batch force cancellation ? The force cancellation is an unsafe operation and in general it should be avoided, maybe the per partition API we have currently is enough ? |
@mmaslankaprv: Please chat with Matt and Alexey, and then depending on your conclusion we can close this out? |
Right now it's still a part of https://github.com/redpanda-data/core-internal/issues/48. The epic might be closed, but it may contain open issues and PRs (confusing, I know). Not sure if I'd have a follow-up epic for every epic. For 22.3 we have this one as a catch-all - https://github.com/redpanda-data/core-internal/issues/64. The problem I'd tackle next is figuring out how we'd best groom the backlog of issues in so that issues like this one surface once someone has extra time. |
JIRA Link: CORE-986
The text was updated successfully, but these errors were encountered: