--job-retries with persistence, expiration is not reflected in DB
Bug #543402 reported by
gil michlin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Gearman |
Fix Released
|
High
|
Eric Day | ||
Bug Description
reproduce:
1. start gearmand server with --job-retries=1 and libdrizzle ( you can set 1 to any number but you will have to run again the worker)
2. add reverse job to queue
3. alter the worker and create fatal error after pulling the job
results:
The job will be removed from the gearman status but will still be in DB
desired results:
The job will be removed both from gearman status and DB
Related branches
lp:~eday/gearmand/bug-fixes
- Gearman-developers: Pending requested
-
Diff: 338 lines (+168/-11) (has conflicts)8 files modified.bzrignore (+1/-0)
ChangeLog (+10/-0)
libgearman-server/job.c (+23/-1)
libgearman-server/job.h (+2/-1)
libgearman-server/server.c (+11/-6)
libgearman/connection.c (+2/-2)
libgearman/universal.c (+1/-1)
tests/worker_test.c (+118/-0)
Revision history for this message
| gil michlin (gil-metacafe) wrote | #1 |
| Changed in gearmand: | |
| status: | New → Fix Committed |
| importance: | Undecided → High |
| assignee: | nobody → Eric Day (eday) |
| milestone: | none → 0.13 |
| Changed in gearmand: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
