Ttr and retry
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.1k
- Forks
- 285
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 2
Description
| Q | A |
|---|---|
| Yii version | 2.0.20 |
| PHP version | 7.3 |
| Operating system | Linux |
I am see #249, but I have also error with ttr.
I have job
- ttr = 600
- retry = 3
- driver = redis
The worker 4 start this job (time more, then ttr = 600 sec)
The workers 6, 5, 8 restart this job after 600 s and ended with error, becouse worker 4 still running.
Job is buried, but worker 4 still worked.
After restarting and change ttr to 1000, this job finished after 650 sec.
It is bug?
And also:
If I have long job (ttr = 60*60 = 3600) with retry = 3 and have error in process, the restart this job will be after TTR (3600 sec = 1 h). But I have restart job with error after 10 min.
It is possible?
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
Start with the Redis worker and job configuration described in the report: ttr, retry, and the long-running process. Reproduce both cases using the stated timings and determine whether a worker continues after the job is buried or whether retry timing is incorrect; done means the observed behavior is explained and corrected or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, redis
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100