Specifically with a 2.2.2 installation. However, I believe it has also happened on our 2.2.3 instance as well.
These are not clients that are always connected. Mostly users adhoc connections with sqlline. But we have experienced the issue with a long running java client as well. This effects clients from all machines until we restart the region servers. Sent from my iPhone On Feb 17, 2014, at 11:10 AM, James Taylor <[email protected]> wrote: 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? Thanks, James On Monday, February 17, 2014, Justin Workman <[email protected]> wrote: > 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 > <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>> > 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 > <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>> > wrote: > >> Has anyone observed this behavior? After running for hours or a couple >> days, Phoenix becomes unreachable by JDBC, and sqlline.sh just freezes. >> >> There is no debug output indicating an error. Anyone know how to debug >> this? >> >> -- >> Russell Jurney twitter.com/rjurney [email protected] datasyndrome. >> com >> >
