[ https://issues.apache.org/jira/browse/MAPREDUCE-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193959#comment-13193959 ]
Jason Lowe commented on MAPREDUCE-3585: --------------------------------------- Marking this as a duplicate of MAPREDUCE-3363. The core issue in both is that the RM is unable to differentiate between a new NM adding to the cluster and a lost NM rejoining the cluster when ephemeral ports are configured. > RM unable to detect NMs restart > ------------------------------- > > Key: MAPREDUCE-3585 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3585 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Reporter: Bhallamudi Venkata Siva Kamesh > Priority: Minor > > Suppose say in a single host, there have been multiple NMs configured. In > this case, there should be mechanism to detect the NMs comeback. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira