[
https://issues.apache.org/jira/browse/HBASE-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754293#action_12754293
]
stack commented on HBASE-1795:
------------------------------
+1 committing....
> log recovery doesnt reset the max sequence id, new logfiles can get tossed as
> 'duplicates'
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-1795
> URL: https://issues.apache.org/jira/browse/HBASE-1795
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.0, 0.21.0
> Reporter: ryan rawson
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1795.patch
>
>
> during log recovery, we dont reset Store.maxSeqId, thus new log entries are
> stamped starting off from the old files. This can cause a problem if we fail
> and recover again, since the new mutations are deemed "old" and shouldnt be
> applied in a subsequent recovery scenario.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
