[
https://issues.apache.org/jira/browse/HDFS-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508567#comment-13508567
]
Hadoop QA commented on HDFS-4240:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12555710/HDFS-4240.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3589//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3589//console
This message is automatically generated.
> In nodegroup-aware case, make sure nodes are avoided to place replica if some
> replica are already under the same nodegroup
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-4240
> URL: https://issues.apache.org/jira/browse/HDFS-4240
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Junping Du
> Assignee: Junping Du
> Attachments: HADOOP-9045.patch, HADOOP-9045-v2.patch,
> HADOOP-9045-v3.patch, HADOOP-9045-v4.patch, HDFS-4240.patch
>
>
> In previous implementation for HADOOP-8468, 3rd replica is avoid to place on
> the same nodegroup of 2nd replica. But it didn't provide check on nodegroup
> of 1st replica, so if 2nd replica's rack is not efficient to place replica,
> then it is possible to place 3rd and 1st replica within the same node group.
> We need a change to remove all nodes from available nodes for placing replica
> if there already replica on the same nodegroup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
