[
https://issues.apache.org/jira/browse/MESOS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131331#comment-14131331
]
Alexander Rukletsov commented on MESOS-1773:
--------------------------------------------
If we put the timeout into the {{CommandInfo}} instead of the {{TaskInfo}},
custom executors won't be able to have different timeouts for heterogeneous
tasks. But indeed, having it in the {{CommandInfo}} implies one timeout per
{{containerizer}}, which simplifies the design a lot (no {{max(Task1.timeout,
Task2.timeout, ...)}} needed). I tend to agree with putting it into the
{{CommandInfo}}.
> Make shutdown grace period configurable per task
> ------------------------------------------------
>
> Key: MESOS-1773
> URL: https://issues.apache.org/jira/browse/MESOS-1773
> Project: Mesos
> Issue Type: Improvement
> Components: general, slave
> Reporter: Alexander Rukletsov
> Labels: patch
>
> With [Issue 1571|https://issues.apache.org/jira/browse/MESOS-1571] fixed,
> shutdown grace periods on all levels are dependent on the slave flag. The
> next step is to make it configurable per task.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
