Hi JM, The phoenix.query.threadPoolSize corresponds to the client-side ThreadPoolExecutor size. All threads on the client-side come out of this pool. As new threads are spawned, they get new names using an AtomicLong that is incremented each time - see org.apache.phoenix.job.JobManager.
Are you seeing more than this number of concurrently executing client threads? Thanks, James On Tue, Nov 4, 2014 at 12:09 PM, Jean-Marc Spaggiari <[email protected]> wrote: > Hi all, > > Quick question about phoenix.query.threadPoolSize. What is it really? > > We changed it locally for dev and testing to 20, but we still see hundreds > of Phoenix threads. We can see threads named like: > phoenix-2-thread-1 to phoenix-2-thread-128 > > Seems that there is phoenix-1 to phoenix-20 only, but there is still > hundreds of other threads under them. > > Is there a way to limit that? > > Thanks, > > JM
