hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17407) Correct update of maxFlushedSeqId in HRegion
Date Thu, 05 Jan 2017 08:33:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15800750#comment-15800750

Duo Zhang commented on HBASE-17407:

Can the map in seq accounting be reported to master during a flush?

There used to be a bug that we report the sequence ids in it to master directly that causes
a data loss. Now we will not report the value if there is a flush ongoing.

And I think we have a race in the Segment class. The minSequenceId field is not an AtomicLong,
and not declared as volatile either, but the MutableSegment will update it by calling internalAdd.
I know that for now it may not be a problem as for MutableSegment we do not need this value?
But as I've said many times, this will make others confusing...


> 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

View raw message