Option to rebalance allocations when adding a node to the cluster
Open
stage/needs-discussion
theme/scheduling
type/enhancement
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Currently even when using the new _Spread_ scheduling a new node gets zero allocations unless jobs are redeployed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining Nomad's Spread scheduling behavior and the allocation lifecycle when a node joins the cluster. Define how an opt-in rebalance should work without requiring job redeployment, including its scope and safety conditions. Done means a new node can receive allocations under the selected option and the behavior is covered by appropriate scheduler tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100