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

Hudson commented on YARN-3802:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #231 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/231/])
YARN-3802. Two RMNodes for the same NodeId are used in RM sometimes (xgong: rev 
5b5bb8dcdc888ba1ebc7e4eba0fa0e7e79edda9a)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/resourcetracker/TestNMReconnect.java
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNodeImpl.java
* hadoop-yarn-project/CHANGES.txt


> Two RMNodes for the same NodeId are used in RM sometimes after NM is 
> reconnected.
> ---------------------------------------------------------------------------------
>
>                 Key: YARN-3802
>                 URL: https://issues.apache.org/jira/browse/YARN-3802
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.0
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>             Fix For: 2.8.0
>
>         Attachments: YARN-3802.000.patch, YARN-3802.001.patch
>
>
> Two RMNodes for the same NodeId are used in RM sometimes after NM is 
> reconnected. Scheduler and RMContext use different RMNode reference for the 
> same NodeId sometimes after NM is reconnected, which is not correct. 
> Scheduler and RMContext should always use same RMNode reference for the same 
> NodeId.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to