No, we didn't upgraded. We are using HBase-0.94.1 The issue here is we are not always facing this issue, only once in a while we are facing this issue(2 or 3 times a day).Other times it working without any issue.
Thanks,Sandeep. > Date: Thu, 12 Dec 2013 23:23:18 -0800 > Subject: Re: zookeeper.znode.parent mismatch exception > From: [email protected] > To: [email protected] > > Did you recently upgrade to 0.96? This is a problem I faced with mismatched > clients connecting to an 0.96 cluster. Starting in that version, the root > node for zookeeper chanced from /hbase to /hbase-unsecure (if in unsecure > mode). > > > On Thu, Dec 12, 2013 at 10:47 PM, Sandeep L <[email protected]>wrote: > > > Hi, > > Our production cluster is in distributed mode with 5 servers as zookeeper > > quorum. > > While accessing production HBase server from our application we are > > getting zookeeper.znode.parent mismatch exception. > > Following is exception in our log files: > > from org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker in > > pool-67467-thread-1Check the value configured in 'zookeeper.znode.parent'. > > There could be a mismatch with the one configured in the master. > > > > We checked all hbase-site.xml files to find any mismatches in > > configurations, but no luck all configuration files same. We don't have any > > configuration with name zookeeper.znode.parent in hbase-site.xml, but I > > have one configuration with same name in hbase-defalut.xml with value as > > /hbase. > > In our application server we don't have any file with name > > hbase-default.xml, but we have hbase-site.xml in it. > > > > Can someone help us to resolve this issue. > > > > Thanks,Sandeep.
