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 81F1611982 for ; Thu, 18 Sep 2014 20:29:36 +0000 (UTC) Received: (qmail 40791 invoked by uid 500); 18 Sep 2014 20:29:36 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 40604 invoked by uid 500); 18 Sep 2014 20:29:36 -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 40578 invoked by uid 99); 18 Sep 2014 20:29:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2014 20:29:36 +0000 Date: Thu, 18 Sep 2014 20:29:36 +0000 (UTC) From: "Mikhail Antonov (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-11462) MetaTableAccessor shouldn't use ZooKeeeper 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-11462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov updated HBASE-11462: ------------------------------------ Status: Open (was: Patch Available) > MetaTableAccessor shouldn't use ZooKeeeper > ------------------------------------------ > > Key: HBASE-11462 > URL: https://issues.apache.org/jira/browse/HBASE-11462 > Project: HBase > Issue Type: Improvement > Components: Client, Zookeeper > Affects Versions: 2.0.0 > Reporter: Mikhail Antonov > Assignee: Mikhail Antonov > Fix For: 2.0.0 > > > After committing patch for HBASE-4495, there's an further improvement which can be made (discussed originally on review board to that jira). > We have MetaTableAccessor and MetaTableLocator classes. First one is used to access information stored in hbase:meta table. Second one is used to deal with ZooKeeper state to find out region server hosting hbase:meta, wait for it to become available and so on. > MetaTableAccessor, in turn, should only operate on the meta table content, so shouldn't need ZK. The only reason why MetaTableAccessor is using ZK - when callers request assignment information, they can request location of meta table itself, which we can't read from meta, so in that case MetaTableAccessor relays the call to MetaTableLocator. May be the solution here is to declare that clients of MetaTableAccessor shall not use it to work with meta table itself (not it's content). -- This message was sent by Atlassian JIRA (v6.3.4#6332)