Re: hbase dynamic configuration

These properties can be used on the client side and the server side. I assume you are asking about them on the server side. Unfortunately, these two are not supported yet for dynamic configuration. Thanks. Jerry On Tue, Feb 28, 2017 at 10:00 PM, Rajeshkumar J

hbase dynamic configuration

Hi, Can any one tell me whether we can add the below properties dynamically 1.hbase.client.scanner.timeout.period 2.hbase.rpc.timeout Thanks, Rajeshkumar

Re: Pre-emptive Fast Fail not used for scanners?

Hey Ted, Unfortunately, that change triggers NPEs in the client. I tracked down the source of the NPE as the ScannerCallableWithReplicas not extending RegionServerCallable as ScannerCallable does. I'm running some additional tests now but should have an update shortly. On Tue, Feb 28, 2017 at

Re: Need guidance on getting detailed elapsed times in every stage of processing a request

No I had not. but it looks like what i needed. Thanks Ted. I'll see if I have any more questions after reading this. From: Ted Yu Sent: Tuesday, February 28, 2017 12:47:08 PM To: user@hbase.apache.org Subject: Re: Need guidance on getting

Re: Need guidance on getting detailed elapsed times in every stage of processing a request

Have you looked at: http://hbase.apache.org/book.html#tracing On Tue, Feb 28, 2017 at 12:37 PM, jeff saremi wrote: > I think we need to get detailed information from HBase RegionServer logs > on how a request (read or write) is processed. Specifically speaking, i > need

Need guidance on getting detailed elapsed times in every stage of processing a request

I think we need to get detailed information from HBase RegionServer logs on how a request (read or write) is processed. Specifically speaking, i need to know of say 100 ms time spent in processing a write, how much of it was spent waiting for the HDFS? What is the most efficient way of enabling

Re: Pre-emptive Fast Fail not used for scanners?

Seems to be a bug. Mind trying out this change ? http://pastebin.com/qim48Se9 Thanks On Tue, Feb 28, 2017 at 11:06 AM, James Moore wrote: > The value is true, and I've been able to verify FastFail behavior when > using Gets when I added a few logging statements into the

Re: Pre-emptive Fast Fail not used for scanners?

What's the value for "hbase.client.fast.fail.mode.enabled" ? The default value is false. Cheers On Tue, Feb 28, 2017 at 9:36 AM, James Moore wrote: > We're considering rolling out Pre-Emptive Fast fail to replace a homegrown > solution based on Hystrix for fast failing