Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

There could be a mismatch with the one configured in the master.

There could be a mismatch with the one configured in the master.

New Contributor

question 1)  

hbase> status  

 

give below error

 

ERROR: The node /u01/hbase/zookeeper_data_dir is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master.

 

---------------------------------------

below is my hbase-site.xml configuration

 

<property><name>zookeeper.znode.parent</name><value>/u01/hbase/zookeeper_data_dir</value></property>
<property><name>hbase.master</name><value>192.168.168.165:60000</value></property>
<property><name>hbase.rootdir</name><value>hdfs://192.168.168.165:9000/u01/app/hadoop/dfs_data_dir/hbase_data</value></property>
<property><name>hbase.cluster.distributed</name><value>true</value></property>
<property><name>hbase.zookeeper.property.clientPort</name><value>2222</value></property>
<property><name>hbase.zookeeper.quorum</name><value>192.168.168.165,192.168.168.166,192.168.168.167</value></property>

 

-------------------------------------------

 

Trying to install   cdh , zookeeper & hbase using the tar ball

 

hadoop-2.3.0-cdh5.0.1.tar.gz
zookeeper-3.4.5-cdh5.0.1.tar.gz
hbase-0.96.1.1-cdh5.0.1.tar.gz

 

-----------------------------------------------

 

 

1 REPLY 1

Re: There could be a mismatch with the one configured in the master.

Master Guru
The zookeeper.znode.parent in HBase is used to place the znode path on ZooKeeper's data space. Typically this is left to the default of /hbase in installations. This is not a local or HDFS path.

Was that property intentionally overriden? If so, you will need to ensure your cluster has also used the very same value and started with it.

If your cluster's parent znode is /hbase and the client is instead configured to use /u01/hbase/zookeeper_data_dir, the exception you received may be expected.