hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4651) JobTracker.addNewTracker() unnecessarily resolves already resolved nodes
Date Thu, 13 Nov 2008 08:14:44 GMT

    [ 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.


Mime
View raw message