Re: API review: max_duration on TaskInfo

> On Mar 23, 2018, at 2:21 PM, Zhitao Li wrote: > > Hi everyone, > > I'd like to do an API review for MESOS-8725 > . We are adding an > optional `max_duration` to `TaskInfo` field. If a task does not terminate > within

Re: API review: max_duration on TaskInfo

A quick update: James and I think the name `max_completion_time` is a bit better than `max_duration`. Semantic should remain the same. On Mon, Mar 26, 2018 at 9:52 AM, Zhitao Li wrote: > Hi Benjamin, > > James and I did some quick search about some existing systems. We

Re: API review: max_duration on TaskInfo

Hi Benjamin, James and I did some quick search about some existing systems. We can dig deep into their semantic. Kubernetes has a feature called activeDeadlineSeconds , although it seems to be total scheduling

Re: API review: max_duration on TaskInfo

In the interest of doing our due diligence, have you studied any prior art? For example, I was surprised to notice that htcondor doesn't really provide this as a first class thing: https://lists.cs.wisc.edu/archive/htcondor-users/2006- November/msg00024.shtml I didn't see it in any other systems

API review: max_duration on TaskInfo

Hi everyone, I'd like to do an API review for MESOS-8725 . We are adding an optional `max_duration` to `TaskInfo` field. If a task does not terminate within this duration, built-in executors will kill the task with a new reason