Allocation left in pending state after node lost
Open
stage/needs-verification
theme/scheduling
type/bug
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
See comment trail starting with https://github.com/hashicorp/nomad/issues/3932#issuecomment-398786137
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the comment trail linked from issue #3932, since this issue body provides no files, tests, or entry points. Use that discussion to determine the expected behavior when a node is lost and an allocation remains pending; done means the allocation reaches the agreed valid state instead of staying pending.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100