[
https://issues.apache.org/jira/browse/HDFS-16517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511011#comment-17511011
]
Konstantin Shvachko commented on HDFS-16517:
--------------------------------------------
Looks like the same issue as HADOOP-16161, as [~xinglin] found out.
The fix is equivalent. I did not compare the tests.
Should we just backport [~omalley]?
> In 2.10 the distance metric is wrong for non-DN machines
> --------------------------------------------------------
>
> Key: HDFS-16517
> URL: https://issues.apache.org/jira/browse/HDFS-16517
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.10.1
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> In 2.10, the metric for distance between the client and the data node is
> wrong for machines that aren't running data nodes (ie.
> getWeightUsingNetworkLocation). The code works correctly in 3.3+.
> Currently
>
> ||Client||DataNode||getWeight||getWeightUsingNetworkLocation||
> |/rack1/node1|/rack1/node1|0|0|
> |/rack1/node1|/rack1/node2|2|2|
> |/rack1/node1|/rack2/node2|4|2|
> |/pod1/rack1/node1|/pod1/rack1/node2|2|2|
> |/pod1/rack1/node1|/pod1/rack2/node2|4|2|
> |/pod1/rack1/node1|/pod2/rack2/node2|6|4|
>
> This bug will destroy data locality on clusters where the clients share racks
> with DataNodes, but are running on machines that aren't running DataNodes,
> such as striping federated HDFS clusters across racks.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
