Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D46711838 for ; Tue, 8 Jul 2014 02:07:34 +0000 (UTC) Received: (qmail 28736 invoked by uid 500); 8 Jul 2014 02:07:34 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 28688 invoked by uid 500); 8 Jul 2014 02:07:34 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 28675 invoked by uid 99); 8 Jul 2014 02:07:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2014 02:07:34 +0000 Date: Tue, 8 Jul 2014 02:07:34 +0000 (UTC) From: "Gary Helmling (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11467) New impl of Registry interface not using ZK + new RPCs on master protocol 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/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054424#comment-14054424 ] Gary Helmling commented on HBASE-11467: --------------------------------------- If I understand the intent correctly, moving ClusterId discovery to a master RPC operation creates a sort of chicken-and-egg problem for token authentication. The RPC client needs to know the ClusterId of the cluster it is connecting to in order to select the correct authentication token to use. This was possible with ZK, as the ClusterId was stored in a public znode. If we move retrieval of the cluster ID to an RPC call on master, the client will not be able to authenticate, since, without the ClusterId, it does not know which token to select. I believe this will make token authentication unusable, or else we would have to special case that specific operation and make it _not_ require authentication on the master (which will be tricky in itself since authentication happens on the connection level). > New impl of Registry interface not using ZK + new RPCs on master protocol > ------------------------------------------------------------------------- > > Key: HBASE-11467 > URL: https://issues.apache.org/jira/browse/HBASE-11467 > Project: HBase > Issue Type: Sub-task > Components: Client, Consensus, Zookeeper > Reporter: Mikhail Antonov > Fix For: 2.0.0 > > > Currently there' only one implementation of Registry interface, which is using ZK to get info about meta. Need to create implementation which will be using RPC calls to master the client is connected to. > That includes adding several new methods to master RPC protocol: > - GetMetaRegionLocation > - GetClusterId > - IsTableOnlineState > - GetCurrentNrHRS -- This message was sent by Atlassian JIRA (v6.2#6252)