hashicorp / hashicorp/nomad

return HTTP429 on dispatch if eval broker queue depth is too high

Open
#26,656 0 comments 0 reactions 0 assignees View on GitHub
hcc/jira theme/batch theme/scheduling type/enhancement
Dominant language
Go
Stars
17k
Forks
2.1k
Avg merge
1d 9h
Merged PRs (30d)
105

Description

For clusters that primarily serve dispatch workloads, it could be useful to provide backpressure when the cluster has a long backlog of pending evaluations. For backwards compatibility we'd want this feature to be disabled by default, as well as configurable by the cluster administrator.

(Internal ref https://hashicorp.atlassian.net/browse/NMD-948. See also internal ref https://hashicorp.atlassian.net/browse/NMD-945 for an RFC I'm working on for eval broker concurrency controls and multi-tenancy.)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the issue's proposed backpressure behavior and the referenced NMD-945 RFC for eval broker concurrency controls and multi-tenancy. The work is done when dispatch requests return HTTP 429 at a configurable queue-depth threshold, while the feature remains disabled by default and administrator-configurable.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.