Re: Dead loop for batch put when get WrongRegionException

It seems that the HBASE-13896 is client-side dead loop, but my problem is the region server side dead lock for get row lock. 2015-07-23 11:22 GMT+08:00 Victor Xu : > Any chance that this would be your problem? > https://issues.apache.org/jira/b

Htrace spans not generated for hbase client side code

My question is similar to the below thread, http://apache-hbase.679495.n3.nabble.com/HTrace-td4056705.html I have enabled htrace logging on server side using the below configuration in hbase-site.xml hbase.trace.spanreceiver.classes org.cloudera.htrace.impl.LocalFileSpanReceiver

Re: Dead loop for batch put when get WrongRegionException

Any chance that this would be your problem? https://issues.apache.org/jira/browse/HBASE-13896 On Thu, Jul 23, 2015 at 11:17 AM Louis Hust wrote: > Hi ,all > > We are using batch put to insert rows, and sometimes get the following WARN > in the region server log: > > > 2015-07-23 10:08:49,684 WA

Dead loop for batch put when get WrongRegionException

Hi ,all We are using batch put to insert rows, and sometimes get the following WARN in the region server log: 2015-07-23 10:08:49,684 WARN [B.defaultRpcServer.handler=5,queue=5,port=60020] regionserver.HRegion: Failed getting lock in batch put, row=BHXYHZFIHHR3ECON10100215072399 org.apache.

Re: configurations for compactions

Hi Shushant, Hbase-site just store different values from default values. If you do not write any settings in hbase-site, Hbase uses default settings. You can reach your active Hbase configuration from Hbase's Master and RegionServers web interfaces. In 1.0 Interfaces port changes. If you Hbase ver