Shutdown doesn't handle 'stuck' active jobs
Open
Discussion
needs pull request
Optimization
- Dominant language
- JavaScript
- Stars
- 9.4k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
It seems that if there are any "stuck" active jobs that when doing shutdown, those active jobs seem to remain. It would seem the expected outcome would be that ALL jobs with a status of active ("stuck" or not), after completion of shutdown (after timeout) would be marked as failed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the shutdown path and its timeout handling, then follow how active jobs are transitioned when shutdown completes. Reproduce the case with a stuck active job and verify that every active job is marked failed after the timeout; inspect existing shutdown-related tests if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, redis
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100