[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326494#comment-14326494
]
James Taylor commented on PHOENIX-971:
--------------------------------------
Good points, [~ndimiduk]. Would the following help?
- As a test, create multiple underlying HConnections by tacking on a third
argument to the connection URL:
{code}
jdbc:phoenix:localhost:a
jdbc:phoenix:localhost:b
...
{code}
- Salting 255 ways is somewhat extreme - keep that down in the 16-64 range
- Play around with the phoenix.stats.guidepost.width or
phoenix.stats.guidepost.per.region to control level of parallelism (see
http://phoenix.apache.org/update_statistics.html).
> 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)
