|
My cluster continually repeats the following message on the node that houses cldb:
My zk cluster isn't on this node. In conf/cldb.conf, the host locations for the zk cluster is correct. It appears that this must be hard-coded some place else? I believe this message started occurring after upgrading to the trial for the M5 edition of MapR. |
|
Could you see which maprcli command it is related to? Some commands get its information from Zookeeper and in order to do this you either supply -zkconnect parameter on the input, or it gets it from CLDB, and if none of the above succeed it tries to use localhost. If you see it after cluster restart - it probably happens while CLDB is not fully functioning yet, once cluster stabilizes it should not happen anymore. It looks like it is coming from com.mapr.cliframework.driver.CLIMainDriver dump zkinfo -json.
(09 Mar '12, 11:13)
jacques
This CLI command is not widely used - may be just for support collect. For some reason looks like CLDB passes to the command ZK address as localhost:5181, as I don't see we default to "localhost" anywhere else. Could you double check parameter: "cldb.zookeeper.servers" on CLDB node(s)?
(09 Mar '12, 12:06)
yufeldman ♦♦
@jacuqes: do you have any update on this issue ? I am trying to reproduce the problem and have also looked at the code. There is no hard-coding. As yufeldman wrote above, the value of Zookeeper string is retrieved from CLDB. If the attempt fails, then the command line argument is looked up. If no argument is specified, the CLI command fails, but should not return localhost:5181. The value of ZkConnect string is logged. Could you grep for "ZKConnect" in /opt/mapr/logs/maprcli-root-*.log and copy it here ? For e.g., in my run, I see $: cd /opt/mapr/logs/ $: grep -ri zkconnect * maprcli-root-0.log:2012-03-30 14:01:15,881 INFO com.mapr.baseutils.cldbutils.CLDBRpcCommonUtils [main]: ZKConnect: xx.xx.xx.151:5181,xx.xx.xx.152:5181,xx.xx.xx.156:5181
(02 Apr '12, 18:47)
Prasad B
|
