[
https://issues.apache.org/jira/browse/MESOS-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055385#comment-14055385
]
Timothy St. Clair edited comment on MESOS-1571 at 7/8/14 8:18 PM:
------------------------------------------------------------------
It seems like it has been placed as a static configuration variable for the
slave (machine policy). Why not have it as an option that passes through from
the point of submission? (task/job policy)
Signal escalation is typically task specific. Some tasks may take minutes
while others take sub-seconds.
was (Author: tstclair):
It seems like it has been placed as a static configuration variable for the
slave (machine policy). Why not have it as an option that passes through from
the point of submission? (task/job policy)
Signal escalation is typically task specific. Some tasks may make minutes
while others take sub-seconds.
> 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
>
> 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.2#6252)
