[
https://issues.apache.org/jira/browse/HBASE-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798198#comment-15798198
]
Edward Bortnikov commented on HBASE-17407:
------------------------------------------
[~Apache9] - what is the invariant you are looking for, and how does it affect
the correctness? "Strange intermediate states" is exactly what transactions are
about - they are perfectly fine. Can you substantiate about the data loss case?
Independent on that, you have a point with that maxFlushedSeqId is managed in
too many places, maybe this is a call to action.
> Correct update of maxFlushedSeqId in HRegion
> --------------------------------------------
>
> Key: HBASE-17407
> URL: https://issues.apache.org/jira/browse/HBASE-17407
> Project: HBase
> Issue Type: Bug
> Reporter: Eshcar Hillel
>
> The attribute maxFlushedSeqId in HRegion is used to track the max sequence id
> in the store files and is reported to HMaster. When flushing only part of the
> memstore content this value might be incorrect and may cause data loss.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
