[ https://issues.apache.org/jira/browse/YARN-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809821#comment-13809821 ]
Alejandro Abdelnur commented on YARN-1343: ------------------------------------------ [~bikassaha], on your ask about checking for the node count, I don't think is necessary, if a reconnect is triggered, it means it was found, in the {{ResourceTrackerService.registerNodeManager()}}: {code} RMNode oldNode = this.rmContext.getRMNodes().putIfAbsent(nodeId, rmNode); if (oldNode == null) { this.rmContext.getDispatcher().getEventHandler().handle( new RMNodeEvent(nodeId, RMNodeEventType.STARTED)); } else { LOG.info("Reconnect from the node at: " + host); this.nmLivelinessMonitor.unregister(nodeId); this.rmContext.getDispatcher().getEventHandler().handle( new RMNodeReconnectEvent(nodeId, rmNode)); } {code} thx > NodeManagers additions/restarts are not reported as node updates in > AllocateResponse responses to AMs > ----------------------------------------------------------------------------------------------------- > > Key: YARN-1343 > URL: https://issues.apache.org/jira/browse/YARN-1343 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 2.2.0 > Reporter: Alejandro Abdelnur > Assignee: Alejandro Abdelnur > Priority: Critical > Fix For: 2.2.1 > > Attachments: YARN-1343.patch, YARN-1343.patch, YARN-1343.patch, > YARN-1343.patch > > > If a NodeManager joins the cluster or gets restarted, running AMs never > receive the node update indicating the Node is running. -- This message was sent by Atlassian JIRA (v6.1#6144)