Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # user - how can thrift connect to hbase?


Copy link to this message
-
Re: how can thrift connect to hbase?
周梦想 2012-12-28, 09:04
Hi hua,
The zookeeper is used by HBase for tow main purpose, one is manging every
region server state, the other is managing --ROOT-- table updated by
HMaster.  So most HBase operation will keep touch with zookeeper,  the
thrift server is not an exception.

2012/12/27 hua beatls <[EMAIL PROTECTED]>

> Hi Andy,
>      i have a question about thrift,does thrift server connect to hbase
> through zookeeper?
>      i read the thrift log and find thrift is assign 'request' to different
> regionserver.
>      below is the log:
>      2012-12-27 15:39:27,924 DEBUG
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> Cached location for BT_NET_LOG_000,0000189094114602012122620
> 200107000031857,1356593966233.d20458ecf526a932f602af63002b290e. is
> hadoop1:60020
> 2012-12-27 15:39:27,924 DEBUG
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> Cached location for BT_NET_LOG_000,0000189098696122012122921
> 000107000031857,1356593966233.c1f127dc9de117605ea332f27b0b3775. is
> hadoop1:60020
> 2012-12-27 15:39:28,563 DEBUG org.apache.hadoop.hbase.client.MetaScanner:
> Scanning .META. starting at
> row=BT_NET_LOG_000,0000189094114602012122620200107000031857,00000
> 000000000 for max=10 rows using
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@52313a4e
> 2012-12-27 15:45:14,850 DEBUG
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> Removed BT_NET_LOG_000,0000153910000002012120115134001000000
> 272,1356589842295.5c84298f6889734514903fffc9582689. for
> tableName=BT_NET_LOG_000 from cache because of
> 0000189002087912012120100000107000031857
> 2012-12-27 15:45:14,853 DEBUG
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> Retry 1, sleep for 1000ms!
> 2012-12-27 15:45:15,379 DEBUG org.apache.hadoop.hbase.client.MetaScanner:
> Scanning .META. starting at
> row=BT_NET_LOG_000,0000153910000002012120115134001000000272,00000
> 000000000 for max=10 rows using
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@52313a4e
> 2012-12-27 15:45:15,384 DEBUG
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> locateRegionInMeta parentTable=.META., metaLocation={region> .META.,,1.1028785192, hostname=hadoop1, port=60020}, attempt=0 of 10
> failed; retrying after sleep of 1000 because: the only available region for
> the required row is a
> split parent, the daughters should be online soon:
>
> BT_NET_LOG_000,0000153910000002012120115134001000000272,1356589842295.5c84298f6889734514903fffc9582689.
> 2012-12-27 15:45:15,856 DEBUG org.apache.hadoop.hbase.client.MetaScanner:
> Scanning .META. starting at
> row=BT_NET_LOG_000,0000189001962242012122322200106000000559,00000
> 000000000 for max=10 rows using
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@52313a4e
> 2012-12-27 15:45:15,859 DEBUG
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> Cached location for BT_NET_LOG_000,0000189001962242012122322
> 200106000000559,1356594314689.23d2fce6f5b6912e39eb7bdf22a069b3. is
> hadoop3:60020
> 2012-12-27 15:45:16,387 DEBUG org.apache.hadoop.hbase.client.MetaScanner:
> Scanning .META. starting at
> row=BT_NET_LOG_000,0000189001962242012122322200106000000559,00000
> 000000000 for max=10 rows using
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@52313a4e
> 2012-12-27 15:45:17,638 DEBUG org.apache.hadoop.hbase.client.MetaScanner:
> Scanning .META. starting at
> row=BT_NET_LOG_000,0000153910000002012120115134001000000272,00000
> 000000000 for max=10 rows using
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@52313a4e
> 2012-12-27 15:45:17,642 DEBUG
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> Cached location for BT_NET_LOG_000,0000153910000002012120115
> 134001000000272,1356594314689.91a440fc38a1d4d9b0afbf0ebf33e7a8. is
maybe your region data just asigned to hadoop1 and hadoop3?  you could
check hadoop2's state, and increase data and load to test.
Good luck!

Andy