palantir / palantir/conjure-java-runtime
Introduce backpressure when rate limits are hit
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 95
- Forks
- 96
- Avg merge
- 3h 38m
- Merged PRs (30d)
- 33
Description
What happened?
Currently a client is able to enqueue an unbounded number of requests into the Dispatcher.
What did you want to happen?
One a certain number of requests are enqueued, we should either start throwing 429s back out of the client, or start blocking the threads enqueueing requests to introduce some form of backpressure upstream.
Contributor guide
No contributing guide indexed for this repository
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
The issue identifies the Dispatcher as the component that currently accepts an unbounded request queue. Start by inspecting the Dispatcher and its rate-limit handling, then clarify whether completion means returning 429 responses or blocking enqueueing threads. Done should include a bounded response to sustained rate-limit pressure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100