gresrun / gresrun/jesque

inFlight key creation during pop operation

Open
#127 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
630
Forks
132
PR merge metrics
No merged PRs in 30d

Description

inFlight key is created in jesque_pop.lua and removed just after task was processed.

As far as I understand , this functionality is used to prevent task loss in case worker failure occurs between pop operation and task execution (which is great :-)

If that's the case, my question is why this functionality is supported only when queueType == 'list'?

I would like to add this functionality for queueType == 'zset' and also for RESET_TO_HIGHEST_PRIORITY next queue strategy.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading jesque_pop.lua and tracing how inFlight keys are created and removed for list queues. Compare that flow with zset queues and the RESET_TO_HIGHEST_PRIORITY next-queue strategy; the work is complete when task-loss protection is supported for both requested cases without changing existing list behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, lua, redis
Domain
backend, distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.