[
https://issues.apache.org/jira/browse/HDFS-9779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140030#comment-15140030
]
Hudson commented on HDFS-9779:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #9271 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9271/])
HDFS-9779 . TestReplicationPolicyWithNodeGroup NODE variable picks wrong
(uma.gangumalla: rev a7fce9ab415fcc834ca1d91f913157ffd103fa5f)
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestReplicationPolicyWithNodeGroup.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> TestReplicationPolicyWithNodeGroup NODE variable picks wrong rack value
> -----------------------------------------------------------------------
>
> Key: HDFS-9779
> URL: https://issues.apache.org/jira/browse/HDFS-9779
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.7.2
> Reporter: Kuhu Shukla
> Assignee: Kuhu Shukla
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HDFS-9779.001.patch
>
>
> The DatanodeDescriptor object for {{NODE}} calls the wrong constructor on an
> already created DatanodeDescriptor object. This overwrites the
> networkLocation value to "default-rack" instead of expected value of
> "/d2/r4/n7". I didn't find any other such malformed calls to
> {{DFSTestUtil.getDatanodeDescriptor}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
