hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18145) The flush may cause the corrupt data for reading
Date Fri, 02 Jun 2017 05:42:05 GMT

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

Chia-Ping Tsai commented on HBASE-18145:

bq. withDelayedScannersClose?

bq. May be we need just one List for this scanners to be delayed closed? (deferred closed)..
Like below?
Currently we have just one list for the scanners to be delayed closed. The "memStoreScannersAfterFlush"
stored the new memscanner after flush. Do I overlook something?

> The flush may cause the corrupt data for reading
> ------------------------------------------------
>                 Key: HBASE-18145
>                 URL: https://issues.apache.org/jira/browse/HBASE-18145
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Blocker
>             Fix For: 2.0.0, 1.4.0, 1.3.2
>         Attachments: HBASE-18145.v0.patch
> After HBASE-17887, the store scanner closes the memstore scanner in updating the inner
scanners. The chunk which stores the current data may be reclaimed. So if the chunk is rewrited
before we send the data to client, the client will receive the corrupt data.
> This issue also breaks the TestAcid*.

This message was sent by Atlassian JIRA

View raw message