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 0220310F6C for ; Fri, 17 Jan 2014 02:20:28 +0000 (UTC) Received: (qmail 35490 invoked by uid 500); 17 Jan 2014 02:20:23 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 35356 invoked by uid 500); 17 Jan 2014 02:20:21 -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 35288 invoked by uid 99); 17 Jan 2014 02:20:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jan 2014 02:20:20 +0000 Date: Fri, 17 Jan 2014 02:20:20 +0000 (UTC) From: "Devaraj Das (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-10347) HRegionInfo changes for adding replicaId and MetaEditor/MetaReader changes for region replicas 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-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj Das updated HBASE-10347: -------------------------------- Assignee: Devaraj Das This is the RB request https://reviews.apache.org/r/17018/ > HRegionInfo changes for adding replicaId and MetaEditor/MetaReader changes for region replicas > ---------------------------------------------------------------------------------------------- > > Key: HBASE-10347 > URL: https://issues.apache.org/jira/browse/HBASE-10347 > Project: HBase > Issue Type: Sub-task > Components: Region Assignment > Reporter: Enis Soztutar > Assignee: Devaraj Das > Fix For: 0.99.0 > > > As per parent jira, the cleanest way to add region replicas we think is to actually create one more region per replica per primary region. So for example, if a table has 10 regions with replication = 3, the table would indeed be created with 30 regions. These regions will be handled and assigned individually for AM purposes. > We can add replicaId to HRegionInfo to indicate the replicaId, and use this to differentiate different replicas of the same region. So, primary replica would have replicaId = 0, and the others will have replicaId > 0. > These replicas will share the same regionId prefix, but differ in an appended replicaId. The primary will not contain the replicaId so that no changes would be needed for existing tables. > In meta, the replica regions are kept in the same row as the primary ( so for above example, there will be 10 rows in meta). The servers for the replicas are kept in columns like "server+replicaId". -- This message was sent by Atlassian JIRA (v6.1.5#6160)