Please take a look at the documentation:
https://phoenix.apache.org/tuning.html
On 7/29/19 4:24 AM, Sumanta Gh wrote:
Hi,
When we use Phoenix client, there are by default 10 new
PHOENIX-SCANNER-RENEW-LEASE-threads created.
There are also new threads spawned for hconnection-shared-thread-pool.
Hi,
When we use Phoenix client, there are by default 10 new
PHOENIX-SCANNER-RENEW-LEASE-threads created.
There are also new threads spawned for hconnection-shared-thread-pool. This
thread pool goes upto having max 256 threads.
How can these thread pool sizes be configured using configuration?
com> on behalf of Sergey Soldatov
<sergeysolda...@gmail.com>
Reply-To: "user@phoenix.apache.org" <user@phoenix.apache.org>
Date: Tuesday, May 22, 2018 at 1:45 PM
To: "user@phoenix.apache.org" <user@phoenix.apache.org>
Subject: Re: Phoenix Client threads
Salt
Salting byte is calculated using a hash function for the whole row key
(using all pk columns). So if you are using only one of PK columns in the
WHERE clause, Phoenix is unable to identify which salting byte (bucket
number) should be used, so it runs scans for all salting bytes. All those
threads
Hi,
We have table with key as (type, id1, id2) (type is same for all rows where as
id1 and id2 are unique for each row) which is salted (30 salt buckets)
The load on this table is about 30 queries/sec with each query taking ~6ms
we are using phoenix 4.7.0 non-thin client
we have query like below
