Re: Lease exception

This is the log i got 2017-01-05 11:41:49,629 DEBUG [B.defaultRpcServer.handler=15,queue=0,port=16020] ipc.RpcServer: B.defaultRpcServer.handler=15,queue=0,port=16020: callId: 3 service: ClientService methodName: Scan size: 23 connection: xx.xx.xx.xx:x

Re: How to Configure hbase.client.scanner.timeout.period and hbase.rpc.timeout

bq. number_of_rows: 2147483647 >From the above line in your posted log, somehow your hbase.client.scanner.caching setting didn't take effect. Please make sure you modified the correct hbase-site.xml on client side. You could also set the caching in the application code, simply by invoking

Re: StochasticLoadBalancer questions

For #2, I think it makes sense to try out using request rates for cost calculation. If the experiment result turns out to be better, we can consider using such measure. Thanks On Wed, Jan 11, 2017 at 5:34 PM, Timothy Brown wrote: > Hi, > > I have a couple of questions

StochasticLoadBalancer questions

Hi, I have a couple of questions about the StochasticLoadBalancer. 1) In CostFromRegionLoadFunction.getRegionLoadCost the cost is weights later samples of the RegionLoad more than previous ones. For example, with a queue size of 4 it would be (.5 * load1 + .25*load2 + .125*load3 + .125*load4).

Re: Doubt in Scanner.next()

As refguide states, hbase.client.scanner.caching works with hbase.client.scanner.max.result.size to try and use the network efficiently. Make sure the release you use is 1.1.0+ which had important bug fixes w.r.t. max result size. On Wed, Jan 11, 2017 at 9:46 AM, Josh Elser

Re: Doubt in Scanner.next()

Behind the scenes, the ClientScanner is buffering results from the previous RPC. Ignoring multiple RegionServers for now, the caching value denotes the number of records that were fetched by the ClientScanner in an RPC. When the buffered results are consumed by your client, a new RPC will be

Re: Hbase Support for C#/.Net

Just another C# library which can be used with Apache Phoenix: https://github.com/Azure/hdinsight-phoenix-sharp Dima says it best in how to determine which to use. Manjeet Singh wrote: Hi All, I have to find which is the best way to query on Hbase will give best result options are as below

Re: How to Configure hbase.client.scanner.timeout.period and hbase.rpc.timeout

this is the log I am getting while running 2017-01-05 11:41:49,629 DEBUG [B.defaultRpcServer.handler=15,queue=0,port=16020] ipc.RpcServer: B.defaultRpcServer.handler=15,queue=0,port=16020: callId: 3 service: ClientService methodName: Scan size: 23 connection: hostname:port

Doubt in Scanner.next()

I have hbase.client.scanner.caching as 100. I am scanning a table. For instance say we have 500 rows matching for the current scan. When I give the statement ResultScanner.next() what will happen? whether it will return 100 rows for each next operation or something else Thanks

Re: How to Configure hbase.client.scanner.timeout.period and hbase.rpc.timeout

I have tried setting hbase.client.scanner.caching to 10, 100, 1000 and 1. But it still fails. On Wed, Jan 11, 2017 at 2:17 PM, Yu Li wrote: > Hi Rajeshkumar, > > Simply speaking, in your case I'd suggest to set > hbase.client.scanner.caching > to a small value like 10 but

Re: How to Configure hbase.client.scanner.timeout.period and hbase.rpc.timeout

Hi Rajeshkumar, Simply speaking, in your case I'd suggest to set hbase.client.scanner.caching to a small value like 10 but not zero, and leave the hbase.client.scanner.caching or hbase.rpc.timeout setting as default. Below are some detailed explanation: Setting hbase.client.scanner.caching to