Skip to content

Fix node-removal state handling and pause/resume orchestration - #1246

Open
Hamdy-khader wants to merge 6 commits into
mainfrom
main-node-remove-2
Open

Fix node-removal state handling and pause/resume orchestration#1246
Hamdy-khader wants to merge 6 commits into
mainfrom
main-node-remove-2

Conversation

@Hamdy-khader

Copy link
Copy Markdown
Collaborator

Summary

This PR fixes storage-node removal state handling during node drain/removal workflows and makes the removal lifecycle explicit and resumable.

What changed

  • Added explicit node states for removal progress:

    • pending_removal
    • in_removal
  • Updated distribution/status reporting to treat these states as non-schedulable/unreachable so they are not counted as healthy cluster members.

  • Updated node-removal orchestration to:

    • mark a node as pending_removal before the removal task becomes active
    • transition to in_removal once the orchestration begins
    • resume cleanly on retries without re-running completed phases
    • keep “retry later” behavior when peer nodes are still unavailable or migration work is incomplete
  • Preserved correct phase ordering for:

    • graceful shutdown
    • replica relocation
    • finalization
    • device decommissioning

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants