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 1CED311859 for ; Tue, 13 May 2014 17:34:00 +0000 (UTC) Received: (qmail 5673 invoked by uid 500); 13 May 2014 17:07:20 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 5627 invoked by uid 500); 13 May 2014 17:07:20 -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 5618 invoked by uid 99); 13 May 2014 17:07:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 May 2014 17:07:20 +0000 Date: Tue, 13 May 2014 17:07:20 +0000 (UTC) From: "Francis Liu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10569) Co-locate meta and master 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-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996641#comment-13996641 ] Francis Liu commented on HBASE-10569: ------------------------------------- Thanks for the doc. Itd be great if we could have the list of use cases we are trying to solve. So we have that motivate the design decisions. During the discussion and my chat with Matteo and Jimmy here is what I got: 1. A method to guarantee security acl changes are fully propagated when a acl change is requested 2. Same as #1 but for quota 3. Remove master daemon to simplify deployment/ops 4. Have a designated set of servers system tables will be hosted on. To isolate it from user region workloads. Feel free to add if I missed anything. #3 and #4 directly motivates this patch. Tho it seeems there was an agreement to still hqve designated hosts as masters? It seems to me #1 and #2 are use cases for a synchronous coordination frameowrk (consensus discussion). Which may or may not require system table colocation. Having fault tolerant coordination as a first class primitive is sorely missing. And I believe enable us avoid design choices which would impede horizontal scalability. > Co-locate meta and master > ------------------------- > > Key: HBASE-10569 > URL: https://issues.apache.org/jira/browse/HBASE-10569 > Project: HBase > Issue Type: Improvement > Components: master, Region Assignment > Reporter: Jimmy Xiang > Assignee: Jimmy Xiang > Fix For: 0.99.0 > > Attachments: Co-locateMetaAndMasterHBASE-10569.pdf, hbase-10569_v1.patch, hbase-10569_v2.patch, hbase-10569_v3.1.patch, hbase-10569_v3.patch, master_rs.pdf > > > I was thinking simplifying/improving the region assignments. The first step is to co-locate the meta and the master as many people agreed on HBASE-5487. -- This message was sent by Atlassian JIRA (v6.2#6252)