[
https://issues.apache.org/jira/browse/HDFS-8890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728002#comment-14728002
]
Chris Trezzo commented on HDFS-8890:
------------------------------------
For more details:
# First warning is complaining about the blockpools instance variable in
Balancer#Parameters not being private and not having accessor methods. All of
the other variables in the class are like this.
# The second one is complaining about the Balancer#Parameters constructor
having too many parameters. Currently all of the instance variables are final.
We could rewrite that Balancer#Parameters class to use a builder pattern with
non-final member variables.
I can file a jira to address both of these.
> Allow admin to specify which blockpools the balancer should run on
> ------------------------------------------------------------------
>
> Key: HDFS-8890
> URL: https://issues.apache.org/jira/browse/HDFS-8890
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: balancer & mover
> Reporter: Chris Trezzo
> Assignee: Chris Trezzo
> Attachments: HDFS-8890-trunk-v1.patch, HDFS-8890-trunk-v2.patch,
> HDFS-8890-trunk-v3.patch, HDFS-8890-trunk-v4.patch
>
>
> Currently the balancer runs on all blockpools. Allow an admin to run the
> balancer on a set of blockpools. This will enable the balancer to skip
> blockpools that should not be balanced. For example, a tmp blockpool that has
> a large amount of churn.
> An example of the command line interface would be an additional flag that
> specifies the blockpools by id:
> -blockpools
> BP-6299761-10.55.116.188-1415904647555,BP-47348528-10.51.120.139-1415904199257
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
