Redis driver reserved id repush to wating list before delete
Open
Nobody has claimed this yet.
help wanted
status:to be verified
- Dominant language
- PHP
- Stars
- 1.1k
- Forks
- 285
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 2
Description
What steps will reproduce the problem?
- set ttr=5 , one job sleep 10s
- use supervisor start 10 worker to handle jobs
- push 100 job to queue
sometimes will error, when one jobmoveExpiredbeforedelete
What's expected?
What do you get instead?
multiprocess need data in time sequence, i just give $queue$.reserved item a greater score than time()+ttr , a temporary situation
Additional info
| Q | A |
|---|---|
| Yii version | |
| PHP version | |
| Operating system |
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
Reproduce the Redis queue scenario with ttr=5, a job sleeping for 10 seconds, 10 workers, and 100 queued jobs. Start by examining the moveExpired and delete ordering; done means reserved jobs are not repushed to the waiting list out of sequence or deleted incorrectly under concurrent processing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, redis
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100