[
https://issues.apache.org/jira/browse/MESOS-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169982#comment-14169982
]
Alexander Rukletsov commented on MESOS-1571:
--------------------------------------------
In the current review request we pass the timeout value via containerizers.
However, in order to implement
[https://issues.apache.org/jira/browse/MESOS-1773], a field in the
{{CommandInfo}} protobuf is needed. I would suggest to use this field for the
default value as well and therefore avoid changing containarizers' code. This
can work as follows: in {{Slave::runTask()}} if the task doesn't have the field
{{grace_period}} set, the slave sets it to the default; in the
{{executorEnvironment()}} preparation function we extract the {{grace_period}}
and set the corresponding environment variable. The review request will follow.
> Signal escalation timeout is not configurable
> ---------------------------------------------
>
> Key: MESOS-1571
> URL: https://issues.apache.org/jira/browse/MESOS-1571
> Project: Mesos
> Issue Type: Bug
> Reporter: Niklas Quarfot Nielsen
> Assignee: Alexander Rukletsov
>
> Even though the executor shutdown grace period is set to a larger interval,
> the signal escalation timeout will still be 3 seconds. It should either be
> configurable or dependent on EXECUTOR_SHUTDOWN_GRACE_PERIOD.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
