[ https://issues.apache.org/jira/browse/HDFS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309897#comment-14309897 ]
Hadoop QA commented on HDFS-316: -------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12697066/HDFS-316.3.patch against trunk revision 1425e3d. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/9459//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9459//console This message is automatically generated. > 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)