AnsweredAssumed Answered

CLDB won't start: Rejecting rpc with status 3 as CLDB is waiting for enough copies of kvstore to be avai lable.

Question asked by benoit on Oct 11, 2012
Latest reply on Oct 11, 2012 by benoit
Hi,

I run a small M5 cluster (3 VMs instances), version 2.0.1. Install and initial tests when fine till the point I lost a disk used by MapR (/dev/sdb).

I restarted the node that experienced the failure after replacing the disk, but now I'm not able to restart CLDB.

The logs (see below) tells that it is not able to fine enough copies of kvstore. I can understand that as I replaced the disk. I don't care about losing data (it's a test env), I just wanted to know how to recover from this state.

Thanks,

    2012-10-12 13:17:06,044 INFO CLDBServer [RPC-thread-10]: RPC: PROGRAMID: 2345 PROCEDUREID: 103 from 10.19.251.93:58906 Rejecting rpc with status 3 as CLDB is waiting for enough copies of kvstore to be available.
    2012-10-12 13:17:06,704 INFO CLDBServer [RPC-thread-4]: RPC: PROGRAMID: 2345 PROCEDUREID: 61 from 10.19.251.92:37316 Rejecting rpc with status 3 as CLDB is waiting for enough copies of kvstore to be available.
    2012-10-12 13:17:08,314 INFO CLDBServer [RPC-thread-8]: RPC: PROGRAMID: 2345 PROCEDUREID: 103 from 10.19.251.91:39005 Rejecting rpc with status 3 as CLDB is waiting for enough copies of kvstore to be available.
    2012-10-12 13:17:09,055 INFO CLDBServer [Lookup-thread-1]: RPC: PROGRAMID: 2345 PROCEDUREID: 5 from 10.19.251.92:1111 Rejecting rpc with status 3 as CLDB is waiting for enough copies of kvstore to be available.
    2012-10-12 13:17:09,422 INFO CLDBServer [Lookup-thread-1]: RPC: PROGRAMID: 2345 PROCEDUREID: 5 from 10.19.251.93:1111 Rejecting rpc with status 3 as CLDB is waiting for enough copies of kvstore to be available.

Outcomes