Failed jobs junking up
- Dominant language
- JavaScript
- Stars
- 9.4k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
I'm noticing that my Redis instance is getting clogged with a lot of failed job details. I'm using removeOnComplete for all jobs across the board but I believe/suspect that it's only relevant to successfully finished jobs. The failed ones seem to simply be maintained in the store.
Do they get purged automatically after a period of time or should I be using another flag to force their removal upon failure? I'm logging the details separately so I don't need Redis to retain any of the details.
Thanks.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported behavior with Redis: create jobs using removeOnComplete, let some succeed and others fail, and inspect which records remain. Then trace Kue's failed-job retention and removal behavior and check its documentation for an existing cleanup option. Done means the retention behavior is confirmed and any required option or documentation change is clearly specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, redis
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100