[
https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519603#comment-14519603
]
Jason Lowe commented on YARN-3554:
----------------------------------
I suggest we go with 3 minutes. The retry interval is 10 seconds, so we'll get
plenty of retries in that time if the failure is fast (e.g.: unknown host,
connection refused) and still get a few retries in if the failure is slow
(e.g.: connection timeout).
> Default value for maximum nodemanager connect wait time is too high
> -------------------------------------------------------------------
>
> Key: YARN-3554
> URL: https://issues.apache.org/jira/browse/YARN-3554
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Jason Lowe
> Assignee: Naganarasimha G R
> Attachments: YARN-3554.20150429-1.patch
>
>
> The default value for yarn.client.nodemanager-connect.max-wait-ms is 900000
> msec or 15 minutes, which is way too high. The default container expiry time
> from the RM and the default task timeout in MapReduce are both only 10
> minutes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
