[
https://issues.apache.org/jira/browse/HBASE-14949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heng Chen updated HBASE-14949:
------------------------------
Attachment: hbase-14949.patch
Because the wal is named by its maxSeqId in it. And when replay, it will
sorted by this id.
So when we write entries into new WAL, the new WAL's maxSeqId maybe less than
old WAL.
But we hopes we can replay old WAL first , then new WAL.
So i add one suffix to new WAL
Detail information is in the patch.
> Skip duplicate entries when replay WAL.
> ---------------------------------------
>
> Key: HBASE-14949
> URL: https://issues.apache.org/jira/browse/HBASE-14949
> Project: HBase
> Issue Type: Improvement
> Reporter: Heng Chen
> Attachments: hbase-14949.patch
>
>
> As HBASE-14004 design, there will be duplicate entries in different WAL. It
> happens when one hflush failed, we will close old WAL with 'acked hflushed'
> length, then open a new WAL and write the unacked hlushed entries into it.
> So there maybe some overlap between old WAL and new WAL.
> We should skip the duplicate entries when replay. I think it has no harm to
> current logic, maybe we do it first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
