Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase >> mail # user >> HConnectionManager$HConnectionImplementation.locateRegionInMeta


+
Kireet 2013-05-30, 03:51
+
Anoop John 2013-05-30, 04:16
+
Kireet 2013-05-30, 13:12
Copy link to this message
-
Re: HConnectionManager$HConnectionImplementation.locateRegionInMeta
0.95 client is not compatible with 0.94 cluster. So you cannot use 0.95 client.

Cheers

On May 30, 2013, at 6:12 AM, Kireet <[EMAIL PROTECTED]> wrote:

>
>
> Would there be a problem if our cluster is 0.94 and we use a 0.95 client?
>
> I am not familiar with the HBase code base, but I did a dump of the thread that is actually running (below). It seems like it is related to the issue you mentioned as the running thread is doing the prefetch logic. Would pre-splitting tables help here? We are doing some performance tests and essentially starting from an empty instance.
>
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:503)
> at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1309)
> - locked <0x00000000e10cf830> (a org.apache.zookeeper.ClientCnxn$Packet)
> at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1036)
> at org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.exists(RecoverableZooKeeper.java:172)
> at org.apache.hadoop.hbase.zookeeper.ZKUtil.checkExists(ZKUtil.java:450)
> at org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker.checkIfBaseNodeAvailable(ZooKeeperNodeTracker.java:208)
> at org.apache.hadoop.hbase.zookeeper.RootRegionTracker.waitRootRegionLocation(RootRegionTracker.java:77)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:874)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:987)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:885)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:846)
> at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:234)
> at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:174)
> at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:160)
> at org.apache.hadoop.hbase.client.MetaScanner.access$000(MetaScanner.java:54)
> at org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:133)
> at org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:130)
> at org.apache.hadoop.hbase.client.HConnectionManager.execute(HConnectionManager.java:383)
> at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:130)
> at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:105)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:947)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1002)
> - locked <0x00000000e882f778> (a java.lang.Object)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:889)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:846)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1533)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1418)
> at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:702)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:671)
> at org.apache.hadoop.hbase.client.HTablePool$PooledHTable.get(HTablePool.java:367)
>
> Thanks
> Kireet
>
> On 5/30/13 12:16 AM, Anoop John wrote:
>> Can you have a look at issue HBASE-8476?  Seems related?  A fix is
>> available in HBASE-8346's patch..
>>
>> -Anoop-
>>
>> On Thu, May 30, 2013 at 9:21 AM, Kireet <kireet-Teh5dPVPL8nQT0dZR+[EMAIL PROTECTED]> wrote:
>>
>>> We are running hbase 0.94.6 in a concurrent environment and we are seeing
>>> the majority of our code stuck in this method at the synchronized block
+
Kireet 2013-05-30, 14:01
+
Ted Yu 2013-05-30, 14:26
+
Himanshu Vashishtha 2013-05-30, 16:48
+
Kireet 2013-05-30, 18:28
+
Ted Yu 2013-05-30, 23:38
+
Kireet 2013-05-31, 18:58
+
lars hofhansl 2013-06-01, 05:43
+
Kireet 2013-06-06, 15:25
+
Ted Yu 2013-05-30, 04:23
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB