AnsweredAssumed Answered

Some error about CLDB

Question asked by claymogo on Jul 18, 2013
Latest reply on Jul 18, 2013 by nabeel
Hi

I installed the version M3 to build the cluster. I focus to the feature Direct Access NFS.

When I finished installation,I started the service mapr-warden(before do it,I run some scripts as configure.sh,disksetup follow the online document).BUT I found I can't open the web https://<MCS>:8443

At the same time I found some error in the logs

 #warden.log
<pre>
2013-07-19 16:41:13,688 ERROR com.mapr.job.mngmnt.hadoop.metrics.MaprRPCContext run [Thread-4]: RPC request failed with status: 1

2013-07-19 16:42:00,389 ERROR com.mapr.warden.service.baseservice.Service$ServiceMonitorRun run [cldb_monitor]: Monitor command: [/etc/init.d/mapr-cldb, status]cannot determine if service: cldb is running. Number of retrials exceeded. Closing Zookeeper

2013-07-19 16:45:47,697 ERROR com.mapr.job.mngmnt.hadoop.metrics.MaprRPCContext run [Thread-4]: RPC request failed with status: 1
</pre>

 #cldb.log
<pre>

2013-07-19 16:33:58,648 INFO CLDBServer [Lookup-1]: Rejecting RPC 2345.5 from 10.45.30.11:1111 with status 3 as CLDB is waiting for local kvstore to become master.

2013-07-19 16:35:04,665 INFO CLDBServer [Lookup-7]: Rejecting RPC 2345.5 from 10.45.30.11:1111 with status 3 as CLDB is waiting for local kvstore to become master.

2013-07-19 16:36:14,671 INFO CLDBServer [Lookup-2]: Rejecting RPC 2345.5 from 10.45.30.11:1111 with status 3 as CLDB is waiting for local kvstore to become master.

2013-07-19 16:37:28,675 INFO CLDBServer [Lookup-3]: Rejecting RPC 2345.5 from 10.45.30.11:1111 with status 3 as CLDB is waiting for local kvstore to become master.

2013-07-19 16:38:34,678 INFO CLDBServer [Lookup-2]: Rejecting RPC 2345.5 from 10.45.30.11:1111 with status 3 as CLDB is waiting for local kvstore to become master.

2013-07-19 16:39:49,681 INFO CLDBServer [Lookup-1]: Rejecting RPC 2345.5 from 10.45.30.11:1111 with status 3 as CLDB is waiting for local kvstore to become master.

2013-07-19 16:40:50,006 FATAL CLDB [WaitForLocalKvstore Thread]: CLDBShutdown: CLDB had master lock and was waiting for its local mfs to become Master.Waited for 7 (minutes) but mfs did not become Master. Shutting down CLDB to release master lock.

2013-07-19 16:40:50,006 INFO CLDBServer [WaitForLocalKvstore Thread]: Shutdown: Stopping CLDB

2013-07-19 16:40:50,008 INFO CLDB [Thread-11]: CLDB ShutDown Hook called

2013-07-19 16:40:50,008 INFO ZooKeeperClient [Thread-11]: Setting the clean cldbshutdown flag to true

2013-07-19 16:40:50,019 INFO CLDBServer [HB-2]: Rejecting RPC 2345.33 from 10.45.30.11:5660 with status 30 as this CLDB is shutting down.

2013-07-19 16:40:50,020 INFO CLDBServer [RPC-2]: Rejecting RPC 2345.31 from 10.45.30.11:5660 with status 30 as this CLDB is shutting down.

2013-07-19 16:40:50,021 INFO ZooKeeperClient [Thread-11]: Zookeeper Client: Closing client connection:

2013-07-19 16:40:50,028 INFO CLDBServer [main-EventThread]: The CLDB received notification that a ZooKeeper event of type NodeDeleted occurred on path /datacenter/controlnodes/cldb/active/CLDBMaster

2013-07-19 16:40:50,028 INFO ZooKeeper [Thread-11]: Session: 0x3ff5c070e7000a closed

2013-07-19 16:40:50,028 INFO CLDB [Thread-11]: CLDB shutdown
</pre>

So, I don't know any mistake in my cluster.

regards.

Outcomes