hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17487) Potential data loss when pipeline is pushed to snapshot
Date Thu, 19 Jan 2017 14:17:26 GMT

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

Anoop Sam John commented on HBASE-17487:

Ya if we dont expect the loop to run more than 2 times, lets fail the op.  I feel its ok..

> Potential data loss when pipeline is pushed to snapshot
> -------------------------------------------------------
>                 Key: HBASE-17487
>                 URL: https://issues.apache.org/jira/browse/HBASE-17487
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Minor
>         Attachments: 17487.v1.txt
> In CompactingMemStore#pushPipelineToSnapshot() , there is limit of 3 iterations of pipeline.swap()
call after which an empty ImmutableSegment is used as snapshot.
> However, after 3rd iteration, the return value from swap() is not checked.
> If the 3rd swap() call is successful, the versioned list would be swapped with null in
pipeline and snapshot being overwritten with the empty ImmutableSegment.

This message was sent by Atlassian JIRA

View raw message