[
https://issues.apache.org/jira/browse/HDFS-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293626#comment-13293626
]
Hadoop QA commented on HDFS-3408:
---------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12531809/HDFS-3408.4.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/2645//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2645//console
This message is automatically generated.
> BKJM : Namenode format fails, if there is no BK root
> ----------------------------------------------------
>
> Key: HDFS-3408
> URL: https://issues.apache.org/jira/browse/HDFS-3408
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Reporter: Rakesh R
> Assignee: Rakesh R
> Priority: Minor
> Attachments: BOOKKEEPER-255.patch, HDFS-3408.1.patch,
> HDFS-3408.2.patch, HDFS-3408.3.patch, HDFS-3408.4.patch
>
>
> +scenario:+
> 1) /ledgers/available zNode is not created in ZooKeeper.
> 2) Apply NN formatting using : hadoop namenode -format
> Namenode formatting has dependency with the BookKeeper client and is throwing
> the following exception.
> {noformat}
> 12/05/10 16:41:57 ERROR namenode.NameNode: Exception in namenode join
> java.lang.IllegalArgumentException: Unable to construct journal,
> bookkeeper://10.18.40.155:2183;10.18.40.155:2182;10.18.40.155:2181/NN
> at
> org.apache.hadoop.hdfs.server.namenode.FSEditLog.createJournal(FSEditLog.java:1226)
> at
> org.apache.hadoop.hdfs.server.namenode.FSEditLog.initJournals(FSEditLog.java:242)
> at
> org.apache.hadoop.hdfs.server.namenode.FSEditLog.initSharedJournalsForRead(FSEditLog.java:223)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.<init>(FSImage.java:134)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:718)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1091)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1191)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at
> org.apache.hadoop.hdfs.server.namenode.FSEditLog.createJournal(FSEditLog.java:1224)
> ... 6 more
> Caused by: java.io.IOException: Error initializing zk
> at
> org.apache.hadoop.contrib.bkjournal.BookKeeperJournalManager.<init>(BookKeeperJournalManager.java:191)
> ... 11 more
> Caused by: org.apache.zookeeper.KeeperException$NoNodeException:
> KeeperErrorCode = NoNode
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:111)
> at
> org.apache.bookkeeper.client.BookieWatcher.readBookiesBlocking(BookieWatcher.java:140)
> at org.apache.bookkeeper.client.BookKeeper.<init>(BookKeeper.java:177)
> at org.apache.bookkeeper.client.BookKeeper.<init>(BookKeeper.java:147)
> at
> org.apache.hadoop.contrib.bkjournal.BookKeeperJournalManager.<init>(BookKeeperJournalManager.java:189)
> ... 11 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
