phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Taylor <>
Subject Re: Phoenix becomes unreachable
Date Mon, 17 Feb 2014 18:09:48 GMT
We'll try to repro on our end. Is this on 2.2.3 or on 3.0.0-SNAPSHOT? Does
it happen after the client is in use for a day or only after it's
idle? Next time it happens, can you try doing a
PhoenixDriver.INSTANCE.close() on the client to see if it helps? Are you
able to connect through Phoenix to the server from a new client or one on a
different machine?


On Monday, February 17, 2014, Justin Workman <>

> We experience the same type of issue. After a day or so clients stop being
> able to connect via jdbc, however connecting to hbase using the hbase shell
> works fine.
> Likewise, there doesn't seem to be any log output indicating why, although
> I haven't spent much time trying to investigate. A restart of the hbase
> region servers seems to resolve the issue.
> 5 region servers 16gb heap each. No specific memory setting configured on
> the client, and effects clients from all machines.
> Sent from my iPhone
> On Feb 17, 2014, at 10:24 AM, James Taylor <<javascript:_e(%7B%7D,'cvml','');>>
> wrote:
> How big a heap have you configured on the client and region server? Just a
> wild guess, but it sounds like it could be an OOM error.
> James
> On Monday, February 17, 2014, Russell Jurney <<javascript:_e(%7B%7D,'cvml','');>>
> wrote:
>> Has anyone observed this behavior? After running for hours or a couple
>> days, Phoenix becomes unreachable by JDBC, and just freezes.
>> There is no debug output indicating an error. Anyone know how to debug
>> this?
>> --
>> Russell Jurney datasyndrome.
>> com

View raw message