[ https://issues.apache.org/jira/browse/HDFS-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098017#comment-14098017 ]
Hadoop QA commented on HDFS-6853: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12661881/HDFS-6853.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}. 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.TestHASafeMode org.apache.hadoop.hdfs.server.namenode.TestINodeFile The following test timeouts occurred in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.TestValidateConfigurationSettings org.apache.hadoop.hdfs.server.namenode.ha.TestStandbyCheckpoints org.apache.hadoop.hdfs.server.namenode.ha.TestDelegationTokensWithHA org.apache.hadoop.hdfs.server.namenode.ha.TestHAStateTransitions org.apache.hadoop.hdfs.server.namenode.ha.TestHAMetrics org.apache.hadoop.hdfs.TestHDFSServerPorts {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/7637//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7637//console This message is automatically generated. > MiniDFSCluster.isClusterUp() should not check if null NameNodes are up > ---------------------------------------------------------------------- > > Key: HDFS-6853 > URL: https://issues.apache.org/jira/browse/HDFS-6853 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: James Thomas > Assignee: James Thomas > Attachments: HDFS-6853.patch > > > Suppose we have a two-NN cluster and then shut down one of the NN's (NN0). > When we try to restart the other NN (NN1), we wait for isClusterUp() to > return true, but this will never happen because NN0 is null and isNameNodeUp > returns false for a null NN. -- This message was sent by Atlassian JIRA (v6.2#6252)