hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Feng Honghua (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10275) [89-fb] Guarantee the sequenceID in each Region is strictly monotonic increasing
Date Sat, 04 Jan 2014 04:00:54 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862193#comment-13862193

Feng Honghua commented on HBASE-10275:

For your reference, [HBASE-9465|https://issues.apache.org/jira/browse/HBASE-9465] describes
the problem of no guarantee of serial transaction delivery to peer in case failover or region-move.

In essence, it's hard to fix if we don't synchronize the previous(or worker regionserver which
takes over the hlog pushing for the failed regionserver) and current hosting regionserver
on hlog push. Without synchronization two different regionservers can push hlog entries of
a same region with different pace. Another alternative fix is to guarantee the old hlog entries
of a region have all been pushed to peer before it can be opened by a new regionserver.

> [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

View raw message