AnsweredAssumed Answered

CLDB shut down itself (on VM)

Question asked by tomek_cejner on Feb 26, 2012
Latest reply on May 19, 2016 by maprcommunity
Hello again,
I am running M3 on VMWare image, and observed some instability. For example this may be not the first time when CLDB stopped unexpectedly:

Can you help me understand what may have happened?

2012-02-27 03:35:09,022 FATAL com.mapr.fs.cldb.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.
2012-02-27 03:35:09,022 INFO  com.mapr.fs.cldb.CLDBServer [WaitForLocalKvstore Thread]: Shutdown: Stopping CLDB
2012-02-27 03:35:09,024 INFO  com.mapr.fs.cldb.CLDB [Thread-9]: CLDB ShutDown Hook called
2012-02-27 03:35:09,024 INFO  com.mapr.fs.cldb.zookeeper.ZooKeeperClient [Thread-9]: Zookeeper Client: Closing client connection:
2012-02-27 03:35:09,036 INFO  com.mapr.fs.cldb.CLDBServer [main-EventThread]: ZooKeeper event NodeDeleted on path /datacenter/controlnodes/cldb/active/CLDBMaster
2012-02-27 03:35:09,037 WARN  com.mapr.fs.cldb.zookeeper.ZooKeeperClient [main-EventThread]: ZooKeeperClient : KvStoreContainerInfo read received connection loss exception. Sleeping for 30 Number of retry left 1
2012-02-27 03:35:09,042 INFO  com.mapr.fs.cldb.CLDB [Thread-9]: CLDB shutdown