Gearman Server and Client Libraries

Add option to queue bad jobs

Registered by Eric Day on 2009-10-30

Optionally send jobs that have hit their retry limit to another queue name. For example:

$ gearmand -j 3 -J jobRetriesEvent

As for the queue name, you can also take a page out of other message queue systems and put it in "{functionName}PM" (reversePM) (poison message) for per-function handling. I'm envisioning this because to keep the system consistent, a manager would have to listen to all registered functions' poison messages and currently there's no way to give a job back to gearmand untouched.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.