hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bh V S Kamesh (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3585) RM unable to detect NMs restart
Date Tue, 20 Dec 2011 18:46:31 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173400#comment-13173400

Bh V S Kamesh commented on MAPREDUCE-3585:

If the NMs have been configured to use static ports, we can store the lost NMs information
by their NodeID and hence RM can detect the NM's comeback.
I *think* there should be a mechanism, even if the NMs have been configured to use ephemeral
> 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: Bh V S Kamesh
> 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


View raw message