Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5346711003 for ; Sun, 7 Sep 2014 13:31:29 +0000 (UTC) Received: (qmail 82099 invoked by uid 500); 7 Sep 2014 13:31:29 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 82024 invoked by uid 500); 7 Sep 2014 13:31:28 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 82010 invoked by uid 500); 7 Sep 2014 13:31:28 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 82007 invoked by uid 99); 7 Sep 2014 13:31:28 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Sep 2014 13:31:28 +0000 Date: Sun, 7 Sep 2014 13:31:28 +0000 (UTC) From: "Vaibhav Gumashta (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-7935) Support dynamic service discovery for HiveServer2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124893#comment-14124893 ] Vaibhav Gumashta commented on HIVE-7935: ---------------------------------------- [~thejas] [~alangates] Latest patch addresses review comments. Thanks! > 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 > > > 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)