You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Bh V S Kamesh (Created) (JIRA)" <ji...@apache.org> on 2011/12/20 19:44:30 UTC

[jira] [Created] (MAPREDUCE-3585) RM unable to detect NMs restart

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

        

[jira] [Commented] (MAPREDUCE-3585) RM unable to detect NMs restart

Posted by "Bh V S Kamesh (Commented) (JIRA)" <ji...@apache.org>.
    [ 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 ports.
                
> 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

        

[jira] [Commented] (MAPREDUCE-3585) RM unable to detect NMs restart

Posted by "Vinod Kumar Vavilapalli (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173522#comment-13173522 ] 

Vinod Kumar Vavilapalli commented on MAPREDUCE-3585:
----------------------------------------------------

What are your actual observations when you tried to restart an NM? Few bugs were fixed in the recent past that should have fixed this.
                
> 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

        

[jira] [Resolved] (MAPREDUCE-3585) RM unable to detect NMs restart

Posted by "Jason Lowe (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe resolved MAPREDUCE-3585.
-----------------------------------

    Resolution: Duplicate
    
> 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

        

[jira] [Commented] (MAPREDUCE-3585) RM unable to detect NMs restart

Posted by "Jason Lowe (Commented) (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Updated] (MAPREDUCE-3585) RM unable to detect NMs restart

Posted by "Vinod Kumar Vavilapalli (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated MAPREDUCE-3585:
-----------------------------------------------

    Priority: Minor  (was: Major)

Downgrading priority till we get more details.
                
> 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
>            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