hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-20066) Region sequence id may go backward after split or merge
Date Mon, 26 Feb 2018 00:59:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-20066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Duo Zhang updated HBASE-20066:
------------------------------
    Attachment: HBASE-20066-v1.patch

> Region sequence id may go backward after split or merge
> -------------------------------------------------------
>
>                 Key: HBASE-20066
>                 URL: https://issues.apache.org/jira/browse/HBASE-20066
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 2.0.0-beta-2
>
>         Attachments: HBASE-20066-v1.patch, HBASE-20066.patch
>
>
> The problem is that, now we have markers which will be written to WAL but not in store
file. For a normal region close, we will write a sequence id file under the region directory,
and when opening we will use this as the open sequence id. But for split and merge, we do
not copy the sequence id file to the newly generated regions so the sequence id may go backwards
since when closing the region we will write flush marker and close marker into WAL...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message