Redis store is cluttered with q:search records when using Kue
- Dominant language
- JavaScript
- Stars
- 9.4k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
Hey there, I've been using Kue to create and process jobs and it's working great, but with a minor setback... my redis store is cluttered with records that look like this:
q:search:word:XXXXXXX
After looking around the code, I found that the "q:search" keys is used in 2 places inside kue, what could be causing this problem? Could it be me not doing something to finalize those records?
Thanks
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the two Kue code locations that use the q:search key while reproducing job creation and processing against Redis. Determine which job lifecycle path leaves q:search:word records behind; done means identifying the cause and defining or verifying the expected cleanup behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, redis
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100