[
https://issues.apache.org/jira/browse/HDFS-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15806192#comment-15806192
]
Hadoop QA commented on HDFS-6853:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color}
| {color:red} HDFS-6853 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-6853 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12662523/HDFS-6853.2.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/18094/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was 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.2.patch, 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
