[
https://issues.apache.org/jira/browse/HBASE-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666645#comment-13666645
]
Jeffrey Zhong commented on HBASE-8573:
--------------------------------------
{quote}
When we do this, SplitLogManager.getRegionFlushedSequenceId(this.watcher,
failedServerName, key);, where are the ids coming from? We are getting them
from zk? How do they get into zk from the region open?
{quote}
SplitLogManager.getRegionFlushedSequenceId are called twice: the first one is
in pre filtering edits read from a wal. The other place is called after
HLogSplitter#waitUntilRegionOnline to get up to date sequenced Ids.
During region
open(HRegionServer#postOpenDeployTasks#updateRecoveringRegionLastFlushedSequenceId),
we'll update these ids in ZK to replace the values from master.
ids firstly comes from HMaster and they're only used in pre-filtering. Later of
the replay, these ids are then updated by the values of
HRegion#getMaxStoreSeqIdForLogReplay during region opening.
> Store last flushed sequence id for each store of region for Distributed Log
> Replay
> ----------------------------------------------------------------------------------
>
> Key: HBASE-8573
> URL: https://issues.apache.org/jira/browse/HBASE-8573
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Jeffrey Zhong
> Attachments: hbase-8573.patch, hbase-8573-v1.patch
>
>
> HBASE-7006 stores last flushed sequence id of the region in zookeeper.
> To prevent deleted data from appearing again, we should store last flushed
> sequence id for each store of region in zookeeper.
> See discussion here:
> https://issues.apache.org/jira/browse/HBASE-7006?focusedCommentId=13660428&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13660428
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
