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

Kihwal Lee commented on HDFS-11742:
-----------------------------------

bq.  Do you think that this is still a blocker of the release?
- HDFS-8188 has problems. It will affect many users, if it is included in a 
release as is. I will -1 the release if the issue is not properly addressed.
- I believe this this jira (HDFS-11742) prevents hitting the issue. Thus this 
jira is a release blocker.
- IF HDFS-11742 is included alongwith HDFS-8188 and HDFS-11377, I will retract 
-1 on HDFS-8188. If not, I will maintain -1.

Do you understand the nature of the issue and how it could affect people? If 
so, please review the patch.

> Improve balancer usability after HDFS-8188
> ------------------------------------------
>
>                 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
>         Attachments: balancer2.8.png, HDFS-11742.branch-2.8.patch, 
> HDFS-11742.branch-2.patch, HDFS-11742.trunk.patch, HDFS-11742.v2.trunk.patch
>
>
> 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.3.15#6346)

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

Reply via email to