[ 
https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536579#comment-14536579
 ] 

Hudson commented on YARN-3554:
------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #180 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/180/])
YARN-3554. Default value for maximum nodemanager connect wait time is too high. 
Contributed by Naganarasimha G R (jlowe: rev 
9757864fd662b69445e0c600aedbe307a264982e)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml


> 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
>              Labels: BB2015-05-RFC, newbie
>             Fix For: 2.7.1
>
>         Attachments: YARN-3554-20150429-2.patch, 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)

Reply via email to