[
https://issues.apache.org/jira/browse/HIVE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142328#comment-14142328
]
Lefty Leverenz commented on HIVE-7935:
--------------------------------------
Doc note: This adds 2 new configuration parameters and changes 6 parameter
descriptions, so the wiki needs to be updated for 0.14.0:
* new: *hive.server2.support.dynamic.service.discovery*
* new: *hive.server2.zookeeper.namespace*
* redescribe: *hive.zookeeper.quorum*
* redescribe: *hive.zookeeper.client.port*
* redescribe: *hive.server2.max.start.attempts*
* redescribe: *hive.server2.thrift.bind.host*
* redescribe: *hive.server2.thrift.http.port*
* redescribe: *hive.server2.thrift.port*
(This also changes the definition for *hive.server2.global.init.file.location*,
but that doesn't need documentation.)
Dynamic service discovery for HS2 also needs to be documented in the HS2 setup
doc. Should it be mentioned in JDBC/ODBC docs too?
* [Setting Up HiveServer2 |
https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2]
* [Hive JDBC Driver |
https://cwiki.apache.org/confluence/display/Hive/HiveJDBCInterface]
* [Hive ODBC Driver | https://cwiki.apache.org/confluence/display/Hive/HiveODBC]
Finally, we need a release note.
> Support dynamic service discovery for HiveServer2
> -------------------------------------------------
>
> Key: HIVE-7935
> URL: https://issues.apache.org/jira/browse/HIVE-7935
> Project: Hive
> Issue Type: New Feature
> Components: HiveServer2, JDBC
> Affects Versions: 0.14.0
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Labels: TODOC14
> Fix For: 0.14.0
>
> Attachments: HIVE-7935.1.patch, HIVE-7935.2.patch, HIVE-7935.3.patch,
> HIVE-7935.4.patch, HIVE-7935.5.patch, HIVE-7935.6.patch, HIVE-7935.7.patch,
> HIVE-7935.8.patch
>
>
> To support Rolling Upgrade / HA, we need a mechanism by which a JDBC client
> can dynamically resolve an HiveServer2 to connect to.
> *High Level Design:*
> Whether, dynamic service discovery is supported or not, can be configured by
> setting HIVE_SERVER2_SUPPORT_DYNAMIC_SERVICE_DISCOVERY. ZooKeeper is used to
> support this.
> * When an instance of HiveServer2 comes up, it adds itself as a znode to
> ZooKeeper under a configurable namespace (HIVE_SERVER2_ZOOKEEPER_NAMESPACE).
> * A JDBC/ODBC client now specifies the ZooKeeper ensemble in its connection
> string, instead of pointing to a specific HiveServer2 instance. The JDBC
> driver, uses the ZooKeeper ensemble to pick an instance of HiveServer2 to
> connect for the entire session.
> * When an instance is removed from ZooKeeper, the existing client sessions
> continue till completion. When the last client session completes, the
> instance shuts down.
> * All new client connection pick one of the available HiveServer2 uris from
> ZooKeeper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
