[ https://issues.apache.org/jira/browse/HDFS-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546618#comment-13546618 ]
Hadoop QA commented on HDFS-4154: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12562773/HDFS-4154.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {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:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3791//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3791//console This message is automatically generated. > BKJM: Two namenodes usng bkjm can race to create the version znode > ------------------------------------------------------------------ > > Key: HDFS-4154 > URL: https://issues.apache.org/jira/browse/HDFS-4154 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha > Affects Versions: 3.0.0, 2.0.3-alpha > Reporter: Ivan Kelly > Assignee: Han Xiao > Attachments: HDFS-4154.patch > > > nd one will get the following error. > 2012-11-06 10:04:00,200 INFO > hidden.bkjournal.org.apache.zookeeper.ClientCnxn: Session establishment > complete on server 109-231-69-172.flexiscale.com/109.231.69.172:2181, > sessionid = 0x13ad528fcfe0005, negotiated timeout = 4000 > 2012-11-06 10:04:00,710 FATAL > org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join > java.lang.IllegalArgumentException: Unable to construct journal, > bookkeeper://109.231.69.172:2181;109.231.69.173:2181;109.231.69.174:2181/hdfsjournal > at > org.apache.hadoop.hdfs.server.namenode.FSEditLog.createJournal(FSEditLog.java:1251) > at > org.apache.hadoop.hdfs.server.namenode.FSEditLog.initJournals(FSEditLog.java:226) > at > org.apache.hadoop.hdfs.server.namenode.FSEditLog.initSharedJournalsForRead(FSEditLog.java:206) > at > org.apache.hadoop.hdfs.server.namenode.FSImage.initEditLog(FSImage.java:657) > at > org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:590) > at > org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:259) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:544) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:423) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:385) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:401) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:435) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:611) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:592) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1135) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1201) > 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:1249) > ... 14 more > Caused by: java.io.IOException: Error initializing zk > at > org.apache.hadoop.contrib.bkjournal.BookKeeperJournalManager.<init>(BookKeeperJournalManager.java:233) > ... 19 more > Caused by: > hidden.bkjournal.org.apache.zookeeper.KeeperException$NodeExistsException: > KeeperErrorCode = NodeExists for /hdfsjournal/version > at > hidden.bkjournal.org.apache.zookeeper.KeeperException.create(KeeperException.java:119) > at > hidden.bkjournal.org.apache.zookeeper.KeeperException.create(KeeperException.java:51) > at > hidden.bkjournal.org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:778) > at > org.apache.hadoop.contrib.bkjournal.BookKeeperJournalManager.<init>(BookKeeperJournalManager.java:222) > ... 19 more -- 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