[
https://issues.apache.org/jira/browse/HADOOP-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Gummadi updated HADOOP-3780:
---------------------------------
Attachment: HADOOP18-3780.patch
Attached the patch for branch 18.
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] -1 javadoc. The javadoc tool appears to have generated 1
warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total
number of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
The javadoc warning is not related to this patch.
Unit tests also passed on my machine in branch 18.
> 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, HADOOP18-3780.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.
