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 "Amar Kamat (JIRA)" <ji...@apache.org> on 2008/11/13 09:14:44 UTC
[jira] Commented: (HADOOP-4651) JobTracker.addNewTracker()
unnecessarily resolves already resolved nodes
[ https://issues.apache.org/jira/browse/HADOOP-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647223#action_12647223 ]
Amar Kamat commented on HADOOP-4651:
------------------------------------
Note that the resolution happens only when a new tracker joins hence this should not be a big hit but its a bug.
> JobTracker.addNewTracker() unnecessarily resolves already resolved nodes
> ------------------------------------------------------------------------
>
> Key: HADOOP-4651
> URL: https://issues.apache.org/jira/browse/HADOOP-4651
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amar Kamat
>
> _hostnameToNodeMap_ maintains a map from _hostname_ to _resolved-address_. {{JobTracker.addNewTracker()}} resolves a node's address if the node is not present in _hostnameToNodeMap_ but uses _tracker-name_ to index into _hostnameToNodeMap_ instead of _hostname_.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.