mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhitao Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-8725) Support max_duration for tasks
Date Mon, 26 Mar 2018 21:53:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414617#comment-16414617
] 

Zhitao Li commented on MESOS-8725:
----------------------------------

One minor decision I'm making is to require all tasks in the same group to have the same `max_duration`
(either all absent, or carries the same value).

Keeping this as record here.

> Support max_duration 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)

Mime
View raw message