[
https://issues.apache.org/jira/browse/HBASE-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-10347:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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: Enis Soztutar
> Fix For: 0.99.0, hbase-10070
>
> Attachments: hbase-10347_redo_v4.patch, hbase-10347_redo_v5.patch,
> hbase-10347_redo_v6.patch, hbase-10347_redo_v7.patch,
> hbase-10347_redo_v8.patch
>
>
> 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)
