Scaling a job with previously-failed allocs results in deployments with an inconsistent "Desired" number
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
In this situation, I had 3 previous failures in a job with count=100, and then tried to scale it to 130; resulted in my deployment reporting that I desired 127:
This affects the UI as well; impacting both the deployment.desired number as shown in the top panel, as well as the eventual steady state of 3 remaining-failed allocs shown in the bottom panel
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the scaling scenario with a count of 100, three previously failed allocations, and a scale to 130; inspect the deployment's reported Desired value and the UI panels. Done means the deployment reports the requested desired count and the failed allocations do not reduce the eventual steady state.
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
- 35/100