You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Sanjeet Malhotra (Jira)" <ji...@apache.org> on 2025/06/28 02:57:00 UTC
[jira] [Resolved] (PHOENIX-7626) Add metrics to capture HTable thread pool utilization and contention
[ https://issues.apache.org/jira/browse/PHOENIX-7626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjeet Malhotra resolved PHOENIX-7626.
---------------------------------------
Fix Version/s: 5.2.2
5.3
Resolution: Fixed
> Add metrics to capture HTable thread pool utilization and contention
> --------------------------------------------------------------------
>
> Key: PHOENIX-7626
> URL: https://issues.apache.org/jira/browse/PHOENIX-7626
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.3
> Reporter: Sanjeet Malhotra
> Assignee: Sanjeet Malhotra
> Priority: Minor
> Fix For: 5.2.2, 5.3
>
>
> PHOENIX-7605 added ability to configure per CQSI HTable thread pool. With this change, someone can either use separate HTable thread pools per CQSI instance or can specify external HTable thread pool by possibly providing an implementation of HTableFactory. (Above two options are in addition to HBase client itself managing the HTable thread pool.) In either of the cases we currently don't have a way to capture utilization/contention at the HTable thread pool level. This Jira aims to add metrics and a framework in general which can be used for CQSI based HTable thread pool and external HTable thread pool both to get visibility on utilization and contention being observed at HTable thread pool level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)