[
https://issues.apache.org/jira/browse/MESOS-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122858#comment-14122858
]
Till Toenshoff commented on MESOS-1571:
---------------------------------------
Using the environment to pass that info seems to fit best when looking at the
things we already pass (e.g. {{MESOS_RECOVERY_TIMEOUT}}), whereas the
{{SlaveInfo}} protobuf is rather limited in additional execution specific
parameters.
However to me this still raises the question on why we prefer using the
environment instead of proto's for such information. One obvious reason
certainly is that we might need to supply information that is needed
immediately before or after starting the {{ExecutorProcess}} but definitely
before it successfully registered, when {{SlaveInfo}} finally becomes available
to him. Despite my above argument being "we already do it that way", are there
better arguments for not adding things to the proto but instead using the
environment for passing the additional parameters?
[~benjaminhindman], [~idownes], [~tnachen] any input for this discussion?
> 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)
