Inflight requests don't get cleaned up?
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 630
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
If in your runnable/callable you do System.exit(1); for example, you end up with an inflight request in redis forever.
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
Start by reproducing the issue with a runnable or callable that invokes System.exit(1), then trace how inflight requests are recorded and cleaned up in Redis. Done means a request that terminates this way does not remain in Redis indefinitely; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, redis
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100