You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Nigel Daley (JIRA)" <ji...@apache.org> on 2008/12/02 20:54:44 UTC
[jira] Commented: (HADOOP-3780) JobTracker should synchronously
resolve the tasktracker's network location when the tracker registers
[ https://issues.apache.org/jira/browse/HADOOP-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652480#action_12652480 ]
Nigel Daley commented on HADOOP-3780:
-------------------------------------
Should this be fixed in 0.18.3 too?
> JobTracker should synchronously resolve the tasktracker's network location when the tracker registers
> -----------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3780
> URL: https://issues.apache.org/jira/browse/HADOOP-3780
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Fix For: 0.19.0
>
> Attachments: HADOOP-3780-v1.1.patch, HADOOP-3780-v1.2.patch, HADOOP-3780-v1.patch
>
>
> This issue is inspired by HADOOP-3620. In JobTracker, the network address of tracker gets resolved asynchronously. Now it can be done inline i.e while the trackers register. This is of great help for HADOOP-3245 where this enhancement makes the design simpler.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.