Error starting NameNode - Hopsworks 0.9

15 views
Skip to first unread message

arse...@gmail.com

unread,
Jan 21, 2020, 10:24:21 AM1/21/20
to Hops
Hi, 
thanks for the reply on my previous post.

Hopsworks 0.9
There are 2 NameNode. If I start a NameNode and after 10 seconds the second NameNode, the services fail with the error below.
If I start the 2 NameNode together, one of them start correctly. The other fail with the same error below.


2020-01-21 08:07:56,728 ERROR io.hops.transaction.handler.RequestHandler: GET_LISTING TX Failed. total tx
 time 302 msec. TotalRetryCount(5) RemainingRetries(4) TX Stats: Setup: 34ms Acquire Locks: 265ms, In Mem
ory Processing: -1ms, Commit Time: -1ms, Total Time: -1ms.
java.lang.IllegalStateException
        at com.google.common.base.Preconditions.checkState(Preconditions.java:134)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem$30.performTask(FSNamesystem.java:5971)
        at io.hops.transaction.handler.TransactionalRequestHandler.execute(TransactionalRequestHandler.java:99)
        at io.hops.transaction.handler.HopsTransactionalRequestHandler.execute(HopsTransactionalRequestHandler.java:50)
        at io.hops.transaction.handler.RequestHandler.handle(RequestHandler.java:65)
        at io.hops.transaction.handler.RequestHandler.handle(RequestHandler.java:60)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCompleteBlocksTotal(FSNamesystem.java:5989)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startCommonServices(FSNamesystem.java:860)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.startCommonServices(NameNode.java:605)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:579)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:761)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:749)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1160)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1185)
2020-01-21 08:07:56,729 ERROR io.hops.transaction.handler.RequestHandler: Rollback the TX
2020-01-21 08:07:56,735 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Failed to start namenode.
java.lang.IllegalStateException
        at com.google.common.base.Preconditions.checkState(Preconditions.java:134)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem$30.performTask(FSNamesystem.java:5971)
        at io.hops.transaction.handler.TransactionalRequestHandler.execute(TransactionalRequestHandler.java:99)
        at io.hops.transaction.handler.HopsTransactionalRequestHandler.execute(HopsTransactionalRequestHandler.java:50)
        at io.hops.transaction.handler.RequestHandler.handle(RequestHandler.java:65)
        at io.hops.transaction.handler.RequestHandler.handle(RequestHandler.java:60)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCompleteBlocksTotal(FSNamesystem.java:5989)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startCommonServices(FSNamesystem.java:860).


Do you understand why?

Thanks,
Antony

Gautier Berthou

unread,
Jan 21, 2020, 10:45:49 AM1/21/20
to arse...@gmail.com, Hops
Hi,

I don't understand why one of the namenode starts and not the other. Can you try to start only one namenode, wait for it to get out of safe mode and then start the second namenode?

Regards,
Gautier


--
You received this message because you are subscribed to the Google Groups "Hops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hopshadoop+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hopshadoop/1a5f5827-1490-4758-925e-10500864e256%40googlegroups.com.

arse...@gmail.com

unread,
Jan 21, 2020, 11:14:19 AM1/21/20
to Hops
Hi,

I have done it. But after some seconds NameNode fails with the same error. I tired with both NameNode.

Regards,
Antony
To unsubscribe from this group and stop receiving emails from it, send an email to hopsh...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages