Two separate CpuBoundWork semaphores – HTTP | JSONRPC
Open
Nobody has claimed this yet.
area/api
area/distributed
ref/IP
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 616
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Is your feature request related to a problem? Please describe.
One of our customers is DDoSing their Icinga 2 via /v1/hosts (a lot of hosts btw.).
That locks up cluster communication entirely.
Describe the solution you'd like
The separate HTTP CpuBoundWork gets e.g. 1 slot or 1/2 of all so that it doesn't bother the cluster.
Describe alternatives you've considered
Put actual processing of HTTP requests in a queue.
Additional context
ref/IP/48306
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how HTTP/JSONRPC requests use CpuBoundWork and how that capacity interacts with cluster communication. The issue provides no file or test names, so first identify the relevant entry points and existing concurrency tests; done means HTTP work has independently bounded capacity without locking up cluster communication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, distributed-systems, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100