[
https://issues.apache.org/jira/browse/PHOENIX-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Isaac updated PHOENIX-7605:
---------------------------------
Description:
Currently we allow the threadpool that is used by the HBase client/HConnection
to be managed externally or at the HTable level.
It might be operationally beneficial to introduce a threadpool at the CQSI
level for the purpose. This can reduce some noisy neighbor issues on the client
side when using a single externally managed threadpool. Also managing an
externally created threadpool can get tricky when ParallelConnections are used.
was:
Currently we allow the threadpool that is used by the HBase client/HConnection
to be managed externally or at the HTable level.
It might be operationally beneficial to introduce a threadpool at the CQSI
level for the purpose. This can reduce some noisy neighbor issues on the client
side. Also managing an externally created threadpool can get tricky when
ParallelConnections are used.
> Allow the threadpool used by HBase client to be managed at the CQSI level
> -------------------------------------------------------------------------
>
> Key: PHOENIX-7605
> URL: https://issues.apache.org/jira/browse/PHOENIX-7605
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.3.0
> Reporter: Jacob Isaac
> Assignee: Ritesh
> Priority: Major
>
> Currently we allow the threadpool that is used by the HBase
> client/HConnection to be managed externally or at the HTable level.
> It might be operationally beneficial to introduce a threadpool at the CQSI
> level for the purpose. This can reduce some noisy neighbor issues on the
> client side when using a single externally managed threadpool. Also managing
> an externally created threadpool can get tricky when ParallelConnections are
> used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
