[
https://issues.apache.org/jira/browse/HBASE-10275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862208#comment-13862208
]
Liyin Tang commented on HBASE-10275:
------------------------------------
The problem you have described is exactly what we want to resolve. Basically if
the sequenceID for each region is strictly monotonic increasing, then in the
case of a region moving from A to B, the replication stream in B would know the
gap/lag for that region in the previous replication stream A.
As you mentioned but slightly different: The fix is to guarantee the old hlog
entries of a region from the previous region server been fully replicated,
before starting to replicate this region from a new region server.
> [89-fb] Guarantee the sequenceID in each Region is strictly monotonic
> increasing
> --------------------------------------------------------------------------------
>
> Key: HBASE-10275
> URL: https://issues.apache.org/jira/browse/HBASE-10275
> Project: HBase
> Issue Type: New Feature
> Reporter: Liyin Tang
> Assignee: Liyin Tang
>
> [HBASE-8741] has implemented the per-region sequence ID. It would be even
> better to guarantee that the sequencing is strictly monotonic increasing so
> that HLog-Based Async Replication is able to delivery transactions in order
> in the case of region movements.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
