[
https://issues.apache.org/jira/browse/HADOOP-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710099#action_12710099
]
Devaraj Das commented on HADOOP-5852:
-------------------------------------
This issue has been resolved in 0.20 IIRC, where the RPC handlers are started
at the end of all initialization. Look at JobTracker.main - it constructs the
JobTracker object and then invokes offerService, and towards the end of
offerService, the interTrackerServer is started..
> JobTracker accepts heartbeats before startup is complete
> --------------------------------------------------------
>
> Key: HADOOP-5852
> URL: https://issues.apache.org/jira/browse/HADOOP-5852
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Todd Lipcon
> Priority: Critical
>
> When the JobTracker is instantiated, it starts listening on its RPC
> interfaces before its startup is complete (ie the constructor is finished
> executing). Because of this, jt.taskScheduler.taskTrackerManager can be null
> when the JT receives a heartbeat from a TT. This throws the JT/TT pair into a
> tight infinite loop (HADOOP-5761)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
