[
https://issues.apache.org/jira/browse/HDFS-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993723#comment-15993723
]
Kihwal Lee commented on HDFS-8818:
----------------------------------
Thanks for the update, [~jojochuang]. That fixes the hang, but the design is
still flawed. Move decision is made then thread pools are created, which
likely only cover a subset of targets in the schedule. Also, the schedule will
less likely make use of all 50 threads anyway. In any case, the moves will all
pile up to the first 25 targets (in our case, 25 thread pools seemed to be the
limit). I don't think it will be faster than the previous one.
> Allow Balancer to run faster
> ----------------------------
>
> Key: HDFS-8818
> URL: https://issues.apache.org/jira/browse/HDFS-8818
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: balancer & mover
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Fix For: 2.8.0, 2.7.4, 3.0.0-alpha1
>
> Attachments: h8818_20150723.patch, h8818_20150727.patch,
> HDFS-8818-branch-2.7.00.patch
>
>
> The original design of Balancer is intentionally to make it run slowly so
> that the balancing activities won't affect the normal cluster activities and
> the running jobs.
> There are new use case that cluster admin may choose to balance the cluster
> when the cluster load is low, or in a maintain window. So that we should
> have an option to allow Balancer to run faster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
