[
https://issues.apache.org/jira/browse/PHOENIX-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Isaac updated PHOENIX-7638:
---------------------------------
Description:
When creating a large number of views, as is evident from the stacktrace -
every call to
getHTableForCoprocessorScan(...) results in a new HTable being created and with
it a new executor pool (by calling getDefaultExecutor() ) as the passed in pool
to the HTable constructor is null.
!Screenshot 2025-06-11 at 9.26.36 AM.png!
Also attaching a thread dump from my local testing
was:
When creating a large number of views, as is evident from the stacktrace -
every call to
getHTableForCoprocessorScan(...) results in a new HTable being created and with
it a new executor pool (by calling getDefaultExecutor() ) as the passed in pool
to the HTable constructor is null.
!Screenshot 2025-06-11 at 9.26.36 AM.png!
> Creating a large number of views leads to OS thread exhaustion
> --------------------------------------------------------------
>
> Key: PHOENIX-7638
> URL: https://issues.apache.org/jira/browse/PHOENIX-7638
> Project: Phoenix
> Issue Type: Bug
> Reporter: Jacob Isaac
> Priority: Major
> Attachments: Screenshot 2025-06-11 at 9.26.36 AM.png
>
>
> When creating a large number of views, as is evident from the stacktrace -
> every call to
> getHTableForCoprocessorScan(...) results in a new HTable being created and
> with it a new executor pool (by calling getDefaultExecutor() ) as the passed
> in pool to the HTable constructor is null.
>
> !Screenshot 2025-06-11 at 9.26.36 AM.png!
>
> Also attaching a thread dump from my local testing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
