[ https://issues.apache.org/jira/browse/HBASE-20066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated HBASE-20066: -------------------------- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > 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, 2.0.0 > > Attachments: HBASE-20066-v1.patch, HBASE-20066-v2.patch, > HBASE-20066-v3.patch, HBASE-20066-v4.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)