[
https://issues.apache.org/jira/browse/MAPREDUCE-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098166#comment-13098166
]
Thomas Graves commented on MAPREDUCE-2749:
------------------------------------------
Hey Vinod, thanks for the feedback. what is we move the
ContainerTokenSecretManager to the top level NodeManager composite and also
pass it into the NodeStatusUpdater so it can update it as soon as it register
with RM? That way by the time the NodeStatusUpdater returns from its start()
routine and can start sending heartbeats to rm everything is initialized and we
won't have any race as to when the RM schedules containers for the rm.
> [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-v2.patch, 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
