Job TTLs for Expiring Jobs
Registered by
Eric Day
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
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
