[
https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713981#comment-13713981
]
Karthik Kambatla commented on YARN-884:
---------------------------------------
[~vinodkv], partly agree with you that they are two different knobs. However,
at least in the current implementation, restarting an NM cleans up all the
containers on it (correct me if I am wrong) including the AM. In that scenario,
having a higher value for AM_EXPIRY will only delay starting the AM. No?
> AM expiry interval should be set to smaller of {am,
> nm}.liveness-monitor.expiry-interval-ms
> -------------------------------------------------------------------------------------------
>
> Key: YARN-884
> URL: https://issues.apache.org/jira/browse/YARN-884
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.0.4-alpha
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Labels: configuration
> Attachments: yarn-884-1.patch
>
>
> As the AM can't outlive the NM on which it is running, it is a good idea to
> disallow setting the am.liveness-monitor.expiry-interval-ms to a value higher
> than nm.liveness-monitor.expiry-interval-ms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
