phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samarth Jain <sama...@apache.org>
Subject Re: How to force timeout when connection fails
Date Thu, 03 Sep 2015 19:44:10 GMT
Zack,

The configs that you overrode do not apply when establishing connection to
HBase via phoenix.
You might want to muck around with hbase.client.retries.number and
zookeeper.recovery.retry
to see if you can get a faster response if HBase is down. I am not an
expert in that area though. Someone from the HBase team should be able to
answer it affirmatively.

- Samarth


On Thu, Sep 3, 2015 at 11:51 AM, Riesland, Zack <Zack.Riesland@sensus.com>
wrote:

> If I use JDBC to DriverManager.getConnection(“myPhoenixURL”,
> myProperties), and HBase is down (say, all the region servers are stopped),
> it takes a VERY long time to timeout.
>
>
>
> In fact, I’m not sure it does. The flow just stops at that statement until
> I bring HBase back to life.
>
>
>
> I tried setting “phoenix.query.timeoutMs” and “phoenix.query.keepAliveMs”
> to 30000 (in the properties passed when creating the connection), hoping
> that would force a timeout after 30 seconds, but it doesn’t seem to help.
>
>
>
> Can someone tell me how to force this to fail quickly, so that I can
> respond appropriately, instead of basically getting stuck?
>
>
>
> Thanks!
>

Mime
View raw message