[ 
https://issues.apache.org/jira/browse/HDFS-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kihwal Lee updated HDFS-11742:
------------------------------
          Resolution: Fixed
        Hadoop Flags: Reviewed
       Fix Version/s: 2.8.3
                      3.0.0-beta1
                      2.7.4
                      2.9.0
    Target Version/s: 2.8.1, 2.7.4, 3.0.0-beta1  (was: 2.7.4, 3.0.0-beta1, 
2.8.1)
              Status: Resolved  (was: Patch Available)

I've committed this to trunk, branch-2, branch-2.8 and branch-2.7.  Did not 
commit it to branch-2.8.2 as it was missing dependencies.  If it doesn't get 
re-branched, I will pull it in to 2.8.2 with all dependencies.

> Improve balancer usability after HDFS-8818
> ------------------------------------------
>
>                 Key: HDFS-11742
>                 URL: https://issues.apache.org/jira/browse/HDFS-11742
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>            Priority: Blocker
>              Labels: release-blocker
>             Fix For: 2.9.0, 2.7.4, 3.0.0-beta1, 2.8.3
>
>         Attachments: balancer2.8.png, balancer_fix.png, 
> HDFS-11742.branch-2.8.patch, HDFS-11742.branch-2.patch, 
> HDFS-11742.trunk.patch, HDFS-11742.v2.trunk.patch, replaceBlockNumOps-8w.jpg
>
>
> We ran 2.8 balancer with HDFS-8818 on a 280-node and a 2,400-node cluster. In 
> both cases, it would hang forever after two iterations. The two iterations 
> were also moving things at a significantly lower rate. The hang itself is 
> fixed by HDFS-11377, but the design limitation remains, so the balancer 
> throughput ends up actually lower.
> Instead of reverting HDFS-8188 as originally suggested, I am making a small 
> change to make it less error prone and more usable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to