[
https://issues.apache.org/jira/browse/HDFS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315025#comment-14315025
]
Tsz Wo Nicholas Sze commented on HDFS-316:
------------------------------------------
> TestMover can be fixed by changing DEFAULT_MAX_NOT_CHANGED_ITERATIONS to
> public and passing it in TestMover.
Indeed, TestMover should be fixed by changing namenodes from Collection<URI> to
Map<URI, List<Path>>. Then, the newNameNodeConnectors with Collection<URI> is
only used by balancer and the one with Map<URI, List<Path>> is only used by
Mover.
> Balancer should run for a configurable # of iterations
> ------------------------------------------------------
>
> Key: HDFS-316
> URL: https://issues.apache.org/jira/browse/HDFS-316
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: balancer & mover
> Affects Versions: 2.4.1
> Reporter: Brian Bockelman
> Assignee: Xiaoyu Yao
> Priority: Minor
> Labels: newbie
> Attachments: HDFS-316.0.patch, HDFS-316.1.patch, HDFS-316.2.patch,
> HDFS-316.3.patch
>
>
> The balancer currently exits if nothing has changed after 5 iterations.
> Our site would like to constantly balance a stream of incoming data; we would
> like to be able to set the number of iterations it "does nothing" for before
> exiting; even better would be if we set it to a negative number and could
> continuously run this as a daemon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
