[ https://issues.apache.org/jira/browse/HDFS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505836#comment-13505836 ]
Hadoop QA commented on HDFS-4231: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12555203/BNHAState.patch against trunk revision . {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}. The javadoc tool did not generate any 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 1.3.9) 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.TestFailoverWithBlockTokensEnabled org.apache.hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3571//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3571//console This message is automatically generated. > Introduce HAState for BackupNode > -------------------------------- > > Key: HDFS-4231 > URL: https://issues.apache.org/jira/browse/HDFS-4231 > Project: Hadoop HDFS > Issue Type: Improvement > Components: ha, name-node > Affects Versions: 2.0.2-alpha > Reporter: Konstantin Shvachko > Assignee: Konstantin Shvachko > Attachments: BNHAState.patch > > > Introduce BNHAState backed up by existing BNHAContext. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira