[ https://issues.apache.org/jira/browse/YARN-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805932#comment-13805932 ]
Shinichi Yamashita commented on YARN-1350: ------------------------------------------ Thank you for additional information. I understand that the port number sets 0 to use multiple NodeManager for a test in MiniYARNCluster. And it seems to be easy to understand that there is notes setting it in real cluster in yarn-default.xml description. > 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)