[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326738#comment-14326738
]
Jeffrey Zhong commented on PHOENIX-971:
---------------------------------------
For the singleton ConnectionQueryServices, I noticed another issue is that
HTable and other Phoenix iterators share the same thread pool. I think this is
bad because this may cause not enough threads to do real work by HTable but
just the above worker threads to wait for HTable to finish work.
I'm thinking let HTable manage its own thread pool and JobManager controls
another one. Basically we have two thread pools for each
ConnectionQueryServices instance.
> 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)
