Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 11 Sep 2014 13:12:34 +0000 (UTC)
From: "Vaibhav Gumashta (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12738357.1409642449000.9003.1410441154156@Atlassian.JIRA>
In-Reply-To: <JIRA.12738357.1409642449000@Atlassian.JIRA>
References: <JIRA.12738357.1409642449000@Atlassian.JIRA>
 <JIRA.12738357.1409642449494@arcas>
Subject: [jira] [Updated] (HIVE-7935) Support dynamic service discovery for
 HiveServer2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vaibhav Gumashta updated HIVE-7935:
-----------------------------------
    Attachment: HIVE-7935.5.patch

[~thejas] v5 adds support for:
1. A notification from ZK to HiveServer2 when the corresponding node is deleted from ZK, which sets the de-registered flag true on the server instance.
2. Better naming of znode.
3. Closing of the last client session on a de-registered HiveServer2 instance shuts down that instance. 
4. Znode ACL are now: OPEN_ACL_UNSAFE - meaning only read only access to the world.

> 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
>             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
>
>
> 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)