[
https://issues.apache.org/jira/browse/HBASE-10275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862190#comment-13862190
]
Feng Honghua commented on HBASE-10275:
--------------------------------------
To achieve the goal of in-order (hlog) transaction delivery, also need to
guarantee all the older(smaller) hlog entries in previous regionserver have
been successfully pushed(replicated) to peer before the region is served by the
new regionserver, right? otherwise it's still possible the hlog entries with
smaller sequenceid are pushed(replicated) to peer in previous hosting
regionserver *after* the ones with greater sequenceid in the new/current
hosting regionserver, right?
For region movement in case of regionserver failover(if we deem it another kind
of region movement, though passively), the hlog files containing un-pushed
entries for the region will be handled by a different regionserver other than
the region's new hosting regionserver, under this situation, it needs the
communication/synchronization between these two regionservers to achieve the
region's in-order transaction delivery from the overall perspective.
> [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)
