phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samarth Jain <>
Subject Re: Phoenix JDBC driver hangs/timeouts
Date Sun, 18 Oct 2015 18:25:29 GMT

Please answer the below questions to help us figure out what might be going

1) How many region servers are on the cluster?

2) What is the value configured for hbase.regionserver.handler.count?

3) What kind of queries is your test executing - point look up / range /
aggregate/ full table scan/ with limit clause / with order by ?

4) What does the schema look like for the tables? Are they salted? How big
are the row keys?

5) Are you executing these queries concurrently or serially? If
concurrently, what is the concurrency number?

6) Do you have Phoenix stats enabled? If yes, can you tell us what does the
below query returns for the tables your test is running queries on:
 WHERE PHYSICAL_NAME='your_table_name';

- Samarth

On Sun, Oct 18, 2015 at 11:05 AM, Alok Singh <> wrote:

> HBase/Phoenix Environment:
> HBase 1.1.2/Phoenix 4.5.1
> JDK: 1.7
> Regions: ~1900
> Client environment:
> JDK: 1.8
> Phoenix JDBC Driver: 4.5.1
> hbase.rpc.timeout=600000
> phoenix.query.threadPoolSize=256
> phoenix.query.queueSize=20000
> As part of validation testing, we run a set of queries against our
> production cluster. But, we have been unable to complete a full test run as
> the client performing the test starts timing out after a few minutes.
> Though we run the queries in the same order, no two test runs will hang at
> the same query.  Here is the link to the thread dumps from one such run:
> There are 3 thread dumps in the file, taken few seconds apart.
> The client creates a new JDBC connection for each query
> (DriverManager.getConnection(...)) and closes it after the query is
> complete.
> Any ideas?
> Alok

View raw message