[
https://issues.apache.org/jira/browse/MESOS-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412053#comment-16412053
]
Zhitao Li commented on MESOS-8725:
----------------------------------
{quote}bq.Can you look into whether we could/should implement this in the agent?
{quote}
To recapture our conversation, I think implementing in executor is preferred:
* it is typically executor sending *TASK_KILLED* state so this is following
the convention;
* it is simpler to implement in executor because its lifecycle is as long as
the task so it does not need to checkpoint/recover these information, comparing
to agent which could restart during the duration;
* agent cannot follow kill_policy as what executor do.
> Support deadline for tasks
> --------------------------
>
> Key: MESOS-8725
> URL: https://issues.apache.org/jira/browse/MESOS-8725
> Project: Mesos
> Issue Type: Improvement
> Reporter: Zhitao Li
> Assignee: 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)
