phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ankur5 C <>
Subject Re: Phoenix becomes unreachable
Date Thu, 20 Feb 2014 05:19:09 GMT

I am using Phoenix HBase for quite sometime . Initially I was trying with a pseudo cluster
HBase , with the phoenix-2.2.2.jar in lib directory of HBase and phoenix-2.2.2-client.jar
in my cleint machine . I have the ip host mapping in my client machine's host file. All was
working fine . Now I am trying to deploy my application with pheonix in an HBase cluster environment.
I have placed the phoenix-2.2.2.jar in lib direcrtory of hbase in my region server and client
jar in my client application vm. Now my system becomes idle when my application starts up
, when my application is going to connect to phoenix. However I have tried to in
my master node and have connected phoenix. But from application everything becomes idle. The
same codebase and configuration has been done as was done for pseudo cluster environment when
everything was in one node , however my client in some other remote machine.

Please suggest. Thanks in advance.

Thanks and Regards,
Ankur Chakraborty-----James Taylor <> wrote: ----- 
To: "" <>
From: James Taylor <>
Date: 02/17/2014 10:54PM
Subject: Re: Phoenix becomes unreachable

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. 


On Monday, February 17, 2014, Russell Jurney <> 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 
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

View raw message