You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2015/07/28 02:43:05 UTC
[jira] [Resolved] (HDFS-3619) isGoodBlockCandidate() in Balancer is
not handling properly if replica factor >3
[ https://issues.apache.org/jira/browse/HDFS-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo Nicholas Sze resolved HDFS-3619.
---------------------------------------
Resolution: Not A Problem
Resolving as not-a-problem. Please feel free to reopen if you disagree.
> isGoodBlockCandidate() in Balancer is not handling properly if replica factor >3
> --------------------------------------------------------------------------------
>
> Key: HDFS-3619
> URL: https://issues.apache.org/jira/browse/HDFS-3619
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer & mover
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Junping Du
> Assignee: Junping Du
>
> Let's assume:
> 1. replica factor = 4
> 2. source node in rack 1 has 1st replica, 2nd and 3rd replica are in rack 2, 4th replica in rack3 and target node is in rack3.
> So, It should be good for balancer to move replica from source node to target node but will return "false" in isGoodBlockCandidate(). I think we can fix it by simply making judgement that at least one replica node (other than source) is on the different rack of target node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)