[
https://issues.apache.org/jira/browse/HBASE-20066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375781#comment-16375781
]
stack commented on HBASE-20066:
-------------------------------
Thanks for digging in. Split and Merge are Pv2 so can add the writing of max
sequenceid as a distinct step. Was wondering if we had to write the sequence
id file to the FS. Could we write it into the split/merge procedure persisted
to the Pv2 WAL log.... but that won't work I suppose since replay of Procedure
is AFTER replay of recovery...
On writing the OPEN event to the WAL, we write it before successful OPEN?
> 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)
