Job TTLs for Expiring Jobs

Registered by Eric Day on 2009-08-31

The TTL could either be specified per job from the client (using the new SUBMIT_JOB_OPT protocol extension), or by the server configuration per function. If a job in the queue has not been serviced yet and the TTL expires, the job is removed and never run.

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.

Subscribers

No subscribers.