AnsweredAssumed Answered

CLDB is going down by the command, "maprcli alarm raise"

Question asked by tsubo0423 on Apr 21, 2012
Latest reply on Apr 22, 2012 by sgopinath
We can kill the CLDB with this command:

    $ maprcli alarm raise -alarm VOLUME_ALARM_QUOTA_EXCEEDED -entity node01

The following is the part of log, "/opt/mapr/logs/cldb.log".

----
    2012-04-21 03:03:54,315 ERROR com.mapr.fs.cldb.CLDBServer [pool-1-thread-29]: RPC: PROGRAMID: 2345 PROCEDUREID: 89 REQFROM: 192.168.xxx.xxx:42035 Exception during processing RPC null
    java.lang.NullPointerException
            at com.mapr.fs.cldb.alarms.AlarmsUtil.updateAlarms(AlarmsUtil.java:137)
            at com.mapr.fs.cldb.CLDBServer.updateAlarms(CLDBServer.java:11454)
            at com.mapr.fs.cldb.CLDBServer.processRpc(CLDBServer.java:2822)
            at com.mapr.fs.cldb.CLDBServer.requestArrived(CLDBServer.java:1711)
            at com.mapr.fs.Rpc$RpcExecutor.run(Rpc.java:127)
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
            at java.lang.Thread.run(Thread.java:662)
    2012-04-21 03:03:54,318 ERROR com.mapr.fs.cldb.CLDBServer [pool-1-thread-29]: Thread: TimerEventHandlerThread ID: 37
    2012-04-21 03:03:54,318 ERROR com.mapr.fs.cldb.CLDBServer [pool-1-thread-29]: java.lang.Object.wait(Native Method)
    2012-04-21 03:03:54,318 ERROR com.mapr.fs.cldb.CLDBServer [pool-1-thread-29]: java.lang.Object.wait(Object.java:485)
    2012-04-21 03:03:54,318 ERROR com.mapr.fs.cldb.CLDBServer [pool-1-thread-29]: com.mapr.fs.cldb.timer.TimerEvent$TimerEventHandlerThread.run(TimerEvent.java:109)
    2012-04-21 03:03:54,318 ERROR com.mapr.fs.cldb.CLDBServer [pool-1-thread-29]: java.lang.Thread.run(Thread.java:662)

        **** snip ****

    2012-04-21 03:03:54,324 ERROR com.mapr.fs.cldb.CLDBServer [pool-1-thread-29]: java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
    2012-04-21 03:03:54,324 FATAL com.mapr.fs.cldb.CLDB [pool-1-thread-29]: CLDBShutdown: CldbError
    2012-04-21 03:03:54,324 FATAL com.mapr.fs.cldb.CLDB [pool-1-thread-29]: CLDB Exception
    java.lang.NullPointerException
            at com.mapr.fs.cldb.alarms.AlarmsUtil.updateAlarms(AlarmsUtil.java:137)
            at com.mapr.fs.cldb.CLDBServer.updateAlarms(CLDBServer.java:11454)
            at com.mapr.fs.cldb.CLDBServer.processRpc(CLDBServer.java:2822)
            at com.mapr.fs.cldb.CLDBServer.requestArrived(CLDBServer.java:1711)
            at com.mapr.fs.Rpc$RpcExecutor.run(Rpc.java:127)
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
            at java.lang.Thread.run(Thread.java:662)
    2012-04-21 03:03:54,325 INFO  com.mapr.fs.cldb.CLDBServer [pool-1-thread-29]: Shutdown: Stopping CLDB
    2012-04-21 03:03:54,325 INFO  com.mapr.fs.cldb.CLDB [Thread-9]: CLDB ShutDown Hook called
    2012-04-21 03:03:54,325 INFO  com.mapr.fs.cldb.zookeeper.ZooKeeperClient [Thread-9]: Zookeeper Client: Closing client connection:



----

Outcomes