hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhihai xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3802) Two RMNodes for the same NodeId are used in RM sometimes after NM is reconnected.
Date Thu, 18 Jun 2015 20:56:00 GMT

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

zhihai xu commented on YARN-3802:
---------------------------------

The test failure for TestNodeLabelContainerAllocation is not related to my change because
no test failure is show in the test report: https://builds.apache.org/job/PreCommit-YARN-Build/8286/testReport/

> 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
>         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)

Mime
View raw message