You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2017/01/19 14:47:26 UTC

[jira] [Updated] (HBASE-17487) Throw exception when pushing pipeline to snapshot fails twice

     [ https://issues.apache.org/jira/browse/HBASE-17487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu updated HBASE-17487:
---------------------------
    Summary: Throw exception when pushing pipeline to snapshot fails twice  (was: Potential data loss when pipeline is pushed to snapshot)

> Throw exception when pushing pipeline to snapshot fails twice
> -------------------------------------------------------------
>
>                 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, 17487.v2.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
(v6.3.4#6332)