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 5AEFE7481 for ; Wed, 7 Dec 2011 02:34:07 +0000 (UTC) Received: (qmail 56049 invoked by uid 500); 7 Dec 2011 02:34:07 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 55679 invoked by uid 500); 7 Dec 2011 02:34:06 -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 55663 invoked by uid 500); 7 Dec 2011 02:34:05 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 55652 invoked by uid 99); 7 Dec 2011 02:34:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2011 02:34:05 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2011 02:34:02 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 0F41F103855 for ; Wed, 7 Dec 2011 02:33:42 +0000 (UTC) Date: Wed, 7 Dec 2011 02:33:42 +0000 (UTC) From: "Ashutosh Chauhan (Updated) (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: <694203703.48075.1323225222063.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1788718598.11214.1316995886206.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (HIVE-2467) HA Support for Metastore Server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HIVE-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2467: ----------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) +1 Committed to trunk. Thanks, Thomas for this useful contribution. > HA Support for Metastore Server > -------------------------------- > > Key: HIVE-2467 > URL: https://issues.apache.org/jira/browse/HIVE-2467 > Project: Hive > Issue Type: Improvement > Components: Metastore, Security, Server Infrastructure > Affects Versions: 0.8.0, 0.9.0 > Reporter: Thomas Weise > Assignee: Thomas Weise > Fix For: 0.9.0 > > Attachments: HIVE-2467.2.patch, HIVE-2467.patch > > > We require HA deployment for metastore server for HCatalog: > * Multiple server instances run behind VIP > * Database provides HA > Metastore server instances will need to be able to share any state required for VIP outside RDBMS. As of Hive 0.8 affected conversational state that needs to support VIP/HA setup is limited to current delegation tokens. Is this correct? > We are planning to use ZooKeeper to share current delegation tokens and master keys between nodes of the VIP. ZK is already (optionally) used by Hive for concurrency control. Access to ZK would be limited on the network level or in the future, when ZooKeeper supports security, through Kerberos, similar to NN access. > Currently Hive taps into Hadoop core security delegation token support through extension of > org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager > A solution could amend the Hive specific extension to support: > * Pluggable delegation token and master key store (ZooKeeper as alternative for in-memory AbstractDelegationTokenSecretManager) > * Delegation token retrieval from token store when not found in memory (wrap/extend retrievePassword(...)) > * Cancellation of token in token store > * Purging of expired tokens from token store > http://www.mail-archive.com/hcatalog-user@incubator.apache.org/msg00053.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira