You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Allan Yang (JIRA)" <ji...@apache.org> on 2018/06/13 08:40:00 UTC

[jira] [Created] (HBASE-20727) Persist FlushedSequenceId to speed up WAL split after cluster restart

Allan Yang created HBASE-20727:
----------------------------------

             Summary: Persist FlushedSequenceId to speed up WAL split after cluster restart
                 Key: HBASE-20727
                 URL: https://issues.apache.org/jira/browse/HBASE-20727
             Project: HBase
          Issue Type: New Feature
    Affects Versions: 2.0.0
            Reporter: Allan Yang
            Assignee: Allan Yang
             Fix For: 3.0.0


We use flushedSequenceIdByRegion and storeFlushedSequenceIdsByRegion in ServerManager to record the latest flushed seqids of regions and stores. So during log split, we can use seqids stored in those maps to filter out the edits which do not need to be replayed. But, those maps are not persisted. After cluster restart or master restart, info of flushed seqids are all lost. 
Here I offer a way to persist those info to HDFS, even if master restart, we can still use those info to filter WAL edits and then to speed up replay.



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