hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Omkar Vinit Joshi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1350) Should not add Lost Node by NodeManager reboot
Date Sat, 26 Oct 2013 00:18:31 GMT

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

Omkar Vinit Joshi commented on YARN-1350:
-----------------------------------------

That is mainly for single node cluster to avoid port clashing. For real cluster you should
define a port there. If you agree I will close this as invalid.

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

Mime
View raw message