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 A9C17112CE for ; Tue, 2 Sep 2014 21:05:28 +0000 (UTC) Received: (qmail 32368 invoked by uid 500); 2 Sep 2014 21:05:24 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 32326 invoked by uid 500); 2 Sep 2014 21:05:24 -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 32260 invoked by uid 99); 2 Sep 2014 21:05:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2014 21:05:24 +0000 Date: Tue, 2 Sep 2014 21:05:24 +0000 (UTC) From: "Mikhail Antonov (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: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-11467?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D141= 18746#comment-14118746 ]=20 Mikhail Antonov commented on HBASE-11467: ----------------------------------------- Updated the diff on RB with latest changes. [~stack] Right, I think we need to have a dedicated discussion around maste= r changes/topology. On the question about bq. If we partition the master =E2=80=93 a far-out possibility that hopeful= ly we never have to do where master 1. does tables A-D and master 2. does t= ables E-H, etc. =E2=80=93 then how would this play out? The cluster string = would have to list all masters ? I think the more robust solution would be forwarding from one master to ano= ther (i.e., clearly each master should know full cluster topology anyway, b= ut clients shouldn't have to, they should be able to ask any master they kn= ow, i.e. a client may only know about some subset of masters, and get locat= ion of the master they actually need). More brainstorming is needed here, f= or sure. > 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 > Affects Versions: 2.0.0 > Reporter: Mikhail Antonov > Assignee: Mikhail Antonov > Fix For: 2.0.0 > > Attachments: HBASE-11467.patch, HBASE-11467.patch, HBASE-11467.pa= tch > > > Currently there' only one implementation of Registry interface, which is = using ZK to get info about meta. Need to create implementation which will b= e using RPC calls to master the client is connected to. > Review of early version of patch is here: https://reviews.apache.org/r/24= 296/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)