[
https://issues.apache.org/jira/browse/MESOS-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410505#comment-16410505
]
James Mulcahy commented on MESOS-8725:
--------------------------------------
Is this actually simpler overall? The framework will know the deadline for the
task itself, and could kill the task if that expired, without any changes in
Mesos today. I could see an argument for decentralizing this to the agents if
this was an "expensive" thing to check, but it seems like a relatively low
overhead + low complexity task for a framework to track – even with say,
millions of tasks?
> Support deadline for tasks
> --------------------------
>
> Key: MESOS-8725
> URL: https://issues.apache.org/jira/browse/MESOS-8725
> Project: Mesos
> Issue Type: Improvement
> Reporter: Zhitao Li
> Priority: Major
>
> In our environment, we run a lot of batch jobs, some of which have tight
> timeline. If any tasks in the job runs longer than x hours, it does not make
> sense to run it anymore.
>
> For instance, a team would submit a job which builds a weekly index and
> repeats every Monday. If the job does not finish before next Monday for
> whatever reason, there is no point to keep any task running.
>
> We believe that implementing deadline tracking distributed across our cluster
> makes more sense as it makes the system more scalable and also makes our
> centralized state machine simpler.
>
> One idea I have right now is to add an *optional* *TimeInfo deadline* to
> TaskInfo field, and all default executors in Mesos can simply terminate the
> task and send a proper *StatusUpdate.*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
