[HIVE-7935] Support dynamic service discovery for HiveServer2

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.14.0
• Fix Version/s: 0.14.0
• Component/s: HiveServer2, JDBC
• Labels: TODOC14
• Assignee: Vaibhav Gumashta
• Reporter: Vaibhav Gumashta
• Created: 02/Sep/14 07:20
• Updated: 01/Oct/19 22:07
• Resolved: 16/Sep/14 19:41

Description

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.

Issue Links

• is duplicated by: HIVE-6363 IllegalArgumentException is thrown instead of SQLException
• links to: Review Board
• mentioned in: Page Loading...