[
https://issues.apache.org/jira/browse/HBASE-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104276#comment-13104276
]
dhruba borthakur commented on HBASE-4401:
-----------------------------------------
As it stands today, the hlog has only one type of metadata record: (METAROW,
METAFAMILY, CACHEFLUSH). I am proposing that we add more of these (METAROW,
METAFAMILY, value) where the value will encode the following:
RSPLITS: parent-region-id, children region ids
ROPEN: region-id
RCLOSE: region-id
When a region is split, a (METAROW, METAFAMILY, RSPLIT) record will be inserted
into the Hlog. Similarly, when a region migrates from RS1 to RS2, RS1 will
insert (METAROW, METAFAMILY, RCLOSE) in its Hlog and when the region is opened
by R2, it will insert (METAROW, METAFAMILY, ROPEN) in its transaction log.
The replication stream can then follow the region splits/moves in the order
they were recorded in the Hlog to deliver data in order to the remote HBase
cluster.
> Record log region splits and region moves in the HLog
> -----------------------------------------------------
>
> Key: HBASE-4401
> URL: https://issues.apache.org/jira/browse/HBASE-4401
> Project: HBase
> Issue Type: Improvement
> Components: regionserver, replication
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
>
> It would be nice to record a region splits, region close and region open in
> the transaction log. This will help in in-order delivery of changes for
> HBase cluster replication.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
