[
https://issues.apache.org/jira/browse/HADOOP-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624825#action_12624825
]
Steve Loughran commented on HADOOP-3780:
----------------------------------------
This seems to render the member variable numResolved unimportant, and the
method moot. The numResolved count is now always zero, so getNumResolved() ==
0, so breaking any tests that used this to wait for the cluster to come up.
1. How can I count the #of task trackers under a job tracker?
2. Can this number be passed to getNumResolved() for BC, or can that be deleted
3. numResolved should be deleted; anyone that is using it needs to know their
code has broken.
> 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.
