[
https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025628#comment-15025628
]
Hudson commented on YARN-4132:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #8881 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/8881/])
YARN-4132. Separate configs for nodemanager to resourcemanager (jlowe: rev
4ac6799d4a8b071e0d367c2d709e84d8ea06942d)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNodeStatusUpdater.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/client/RMProxy.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
* hadoop-yarn-project/CHANGES.txt
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/api/ServerRMProxy.java
> Separate configs for nodemanager to resourcemanager connection timeout and
> retries
> ----------------------------------------------------------------------------------
>
> Key: YARN-4132
> URL: https://issues.apache.org/jira/browse/YARN-4132
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Reporter: Chang Li
> Assignee: Chang Li
> Fix For: 2.8.0
>
> Attachments: YARN-4132.2.patch, YARN-4132.3.patch, YARN-4132.4.patch,
> YARN-4132.5.patch, YARN-4132.6.2.patch, YARN-4132.6.patch, YARN-4132.7.patch,
> YARN-4132.patch
>
>
> Being part of the cluster, nodemanagers should try very hard (and possibly
> never give up) to connect to a resourcemanager. Minimally we should have a
> separate config to set how aggressively a nodemanager will connect to the RM
> separate from what clients will do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
