hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1459) FileSystem.getFileCacheHints returns IP addresses rather than hostnames, which breaks 'data-locality' in map-reduce
Date Fri, 08 Jun 2007 20:22:26 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502917
] 

Konstantin Shvachko commented on HADOOP-1459:
---------------------------------------------

Could you please remove redundant
import org.apache.hadoop.io.UTF8
if you change DatanodeInfo.

I think this is the right fix for the time being, although I'm not happy that
# we should keep 2 different identifications for the nodes and that
# we have different ways of node identification in different components of hadoop.

My proposition would be to return back to hostnames instead of ip addresses.
But this of course belongs to a different issue.

> FileSystem.getFileCacheHints returns IP addresses rather than hostnames, which breaks
'data-locality' in map-reduce
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1459
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1459
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.14.0
>            Reporter: Arun C Murthy
>            Assignee: dhruba borthakur
>            Priority: Blocker
>             Fix For: 0.14.0
>
>         Attachments: getHintsIpAddress.patch
>
>
> FileSystem.getFileCacheHints via DFSClient.getHints (post HADOOP-894?) returns IP address
of the datanodes instead of the hostnames which breaks mapping from task-tracker to datanodes
in map-reduce i.e. the system cannot intelligently place maps on datanodes where blocks are
present.
> I have verified that this affects trunk only, branch-0.13.0 seems ok.

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