[
https://issues.apache.org/jira/browse/HBASE-20066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376062#comment-16376062
]
Duo Zhang commented on HBASE-20066:
-----------------------------------
{quote}
When we assign a region, we mark its state as OPENING and we register the
region with the target server before we send the open RPC such that if it
crashes, the OPENING region is recognized as 'belonging' the RS
{quote}
OK. Then let me dig more later. Anyway, we can fix the split and merge first in
this issue.
> 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
> Priority: Critical
>
> 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)
