[
https://issues.apache.org/jira/browse/HDFS-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672042#comment-13672042
]
Hadoop QA commented on HDFS-4240:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12585716/HDFS-4240-branch-2.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4465//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
> Fix For: 3.0.0
>
> Attachments: HADOOP-9045.patch, HADOOP-9045-v2.patch,
> HADOOP-9045-v3.patch, HADOOP-9045-v4.patch, HDFS-4240-branch-2.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