You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2015/10/08 18:02:27 UTC

[jira] [Updated] (YARN-3802) Two RMNodes for the same NodeId are used in RM sometimes after NM is reconnected.

     [ https://issues.apache.org/jira/browse/YARN-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated YARN-3802:
-----------------------------
    Fix Version/s:     (was: 2.8.0)
                   2.6.2
                   2.7.2

I committed this to branch-2.7 and branch-2.6 as well.

> 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.7.2, 2.6.2
>
>         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)