hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9045) In nodegroup-aware case, make sure nodes are avoided to place replica if some replica are already under the same nodegroup
Date Thu, 15 Nov 2012 19:41:13 GMT

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

Tsz Wo (Nicholas), SZE commented on HADOOP-9045:
------------------------------------------------

> ... The findbug problem is not a issue as local variable is used in controlling while-loop.
So it looks no issue for this precommit test.

Hi Junping, although the findbugs warnings are not harmful, we still have to fix it.  Otherwise,
it will fail every build in the future if we commit the patch.
                
> In nodegroup-aware case, make sure nodes are avoided to place replica if some replica
are already under the same nodegroup
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9045
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9045
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.0.2-alpha
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: HADOOP-9045.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

Mime
View raw message