AnsweredAssumed Answered

M3: Moving CLDB - How to control 'target'

Question asked by thealy on Nov 26, 2012
Latest reply on Nov 26, 2012 by Ted Dunning
I am Running V2.0.0 / M3 on small (21) node cluster with most nodes RedHat. I need to migrate the CLDB to a better system before upgrading to V2.1.0. Based on this thread:

and the docs, I added the intended new CLDB ("target"), which is confirmed by the output of:

maprcli dump cldbnodes -zkconnect -json

where the target is the third (last) in the list. I can see the CLDB service periodically starting and stopping.

I'm unsure how to proceed. I know I need to stop the current CLDB, presumably by mapr-warden stop or UI?, and wait > 60 mins for the license timeout.

 1. Do I need to stop the CLDB on the second of three nodes listed by the '...dump cldbnodes..' command also?

 2. What order of actions is necessary to bring up the CLDB on the desired target?

 3. Do I need to stop warden on all the nodes within the cluster and then run configure with the new CLDB address?

Sorry for so many questions on this issue, but I don't want to blow up my CLDB.