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 "Omkar Vinit Joshi (JIRA)" <ji...@apache.org> on 2013/10/26 02:20:30 UTC

[jira] [Resolved] (YARN-1350) Should not add Lost Node by NodeManager reboot

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

Omkar Vinit Joshi resolved YARN-1350.
-------------------------------------

    Resolution: Invalid
      Assignee: Omkar Vinit Joshi

> Should not add Lost Node by NodeManager reboot
> ----------------------------------------------
>
>                 Key: YARN-1350
>                 URL: https://issues.apache.org/jira/browse/YARN-1350
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 3.0.0
>            Reporter: Shinichi Yamashita
>            Assignee: Omkar Vinit Joshi
>         Attachments: NodeState.txt
>
>
> In current trunk, when NodeManager reboots, the node information before the reboot is treated as "LOST".
> This occurs to confirm only Inactive node information at the time of reboot.
> Therefore Lost Node will exist even if NodeManager works in all nodes.
> We should change it not to register Lost Node by the NodeManager reboot.



--
This message was sent by Atlassian JIRA
(v6.1#6144)