[
https://issues.apache.org/jira/browse/MAPREDUCE-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096016#comment-13096016
]
Thomas Graves commented on MAPREDUCE-2749:
------------------------------------------
Steps to reproduce original issue:
on single node cluster:
- configure nm to be use same port as rm. (or another port that is already in
use)
- start rm and nm
- view RM node webui (or logs) and see that the nm is registered
- After node timeout RM expires the node (default value is 600000)
> [MR-279] NM registers with RM even before it starts various servers
> -------------------------------------------------------------------
>
> Key: MAPREDUCE-2749
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2749
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Thomas Graves
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-2749.patch
>
>
> In case NM eventually fails to start the ContainerManager server because of
> say a port clash, RM will have to wait for expiry to detect the NM crash.
> It is desirable to make NM register with RM only after it can start all of
> its components successfully.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
