[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326760#comment-14326760
]
Jeffrey Zhong commented on PHOENIX-971:
---------------------------------------
With one single thread pool, a dead lock situation could even happen as all
available threads are just used for iterators while no threads left for HTable
to do the work. With two thread pools, we can provide isolations. Basically
using JobManager to bound all concurrent query work items in Phoenix space and
let HTable client manage its own thread pool without being affected by other
work items.
Below is the code, I'm referring to:
{code}
return HBaseFactoryProvider.getHTableFactory().getTable(tableName, connection,
getExecutor());
{code}
> Query server
> ------------
>
> Key: PHOENIX-971
> URL: https://issues.apache.org/jira/browse/PHOENIX-971
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Andrew Purtell
> Assignee: Nick Dimiduk
> Fix For: 5.0.0
>
>
> Host the JDBC driver in a query server process that can be deployed as a
> middle tier between lighter weight clients and Phoenix+HBase. This would
> serve a similar optional role in Phoenix deployments as the
> [HiveServer2|https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2]
> does in Hive deploys.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
