You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Tanuj Khurana (Jira)" <ji...@apache.org> on 2024/02/13 00:50:00 UTC

[jira] [Created] (PHOENIX-7213) Don't enforce phoenix.query.queueSize limits

Tanuj Khurana created PHOENIX-7213:
--------------------------------------

             Summary: Don't enforce phoenix.query.queueSize limits
                 Key: PHOENIX-7213
                 URL: https://issues.apache.org/jira/browse/PHOENIX-7213
             Project: Phoenix
          Issue Type: Improvement
            Reporter: Tanuj Khurana


As discussed in [PHOENIX-7117|https://issues.apache.org/jira/browse/PHOENIX-7117]  _*phoenix.query.queueSize*_ limits can cause scan queries on table with lot of regions to fail. I did some profiling and found that each task allocates 48 bytes. So I am adding an enhancement to not enforce this limit (or an infinite queue ) if we set the limit to -1. We still have a limit on the number of tasks that can be executed in parallel controlled by the 
_*phoenix.query.threadPoolSize*_
 
If you don't enforce the limit, the only thing that is limiting is the jvm heap allocated.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)