resque / resque/resque-scheduler
Delayed jobs not getting persisted to redis
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.7k
- Forks
- 477
- PR merge metrics
- No merged PRs in 30d
Description
I'm having trouble getting my delayed jobs showing on resque-web. Looking back on past issues it looks like the reason is that at some point schedules and other data started getting stored in-memory rather than on redis.
It looks like there's a way to force schedule jobs to be persisted on redis (persisted: true). My question is: Is there a way to do this with delayed jobs? (enqueued_at and enqueued_in). I mostly use delayed jobs and it's been inconvenient to not be able to see them on resque-web.
I'll really appreciate any replies. Thanks.
Contributor guide
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
No file or test is named. Start by tracing how delayed jobs using enqueued_at and enqueued_in are stored, then compare that path with schedules using persisted: true and their visibility in resque-web. Done means determining whether delayed jobs can be persisted to Redis and documenting or testing the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, ruby
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100