[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205678#comment-14205678
]
Andrew Purtell commented on PHOENIX-971:
----------------------------------------
bq. Since each RS can act as a Phoenix client, we could implement a thin client
that sends the query from the client to the RS which would most likely handle
at least part of the query.
I don't think that is a good idea. Today's server side parts of Phoenix already
add heap, object allocation, and thread scheduling pressures to the
RegionServer processes. The benefit of a query server as its own process is it
can be separately provisioned sufficient resources to support parallel query
dispatch and final results merging on behalf of a fleet of clients. Trying to
do that inside the RS process instead is I fear a recipe for systemwide
instability.
> Query server
> ------------
>
> Key: PHOENIX-971
> URL: https://issues.apache.org/jira/browse/PHOENIX-971
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Andrew Purtell
>
> 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)
