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

Posted to mapreduce-dev@hadoop.apache.org by "zhihai xu (JIRA)" <ji...@apache.org> on 2015/06/15 00:38:01 UTC

[jira] [Resolved] (MAPREDUCE-6398) Two RMNodes for the same NodeId are used in RM sometimes after NM is reconnected.

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

zhihai xu resolved MAPREDUCE-6398.
----------------------------------
    Resolution: Duplicate

> Two RMNodes for the same NodeId are used in RM sometimes after NM is reconnected.
> ---------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6398
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6398
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.0
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>
> 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)