tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Neumann (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TEPHRA-201) In-progress transactions may become visible when transactions are checkpointed
Date Thu, 08 Dec 2016 21:07:58 GMT

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

Andreas Neumann resolved TEPHRA-201.
------------------------------------
    Resolution: Fixed

> In-progress transactions may become visible when transactions are checkpointed
> ------------------------------------------------------------------------------
>
>                 Key: TEPHRA-201
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-201
>             Project: Tephra
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.0-incubating, 0.9.0-incubating
>            Reporter: Poorna Chandra
>            Assignee: Poorna Chandra
>            Priority: Blocker
>             Fix For: 0.10.0-incubating
>
>
> When a transaction is created, the current in-progress list is attached to the transaction
object. This list is used to filter out in-progress transactions during read.
> The transaction object expects this list to be sorted numerically since it does a binary
search for filtering out the in-progress transactions. 
> When checkpointing feature was added in TEPHRA-96, checkpoints were also added as part
of the in-progress list since data writes from checkpoints also have to be filtered out during
reads. However adding checkpoints broke the sort order. This leads to binary search not working
as expected to filter out in-progress transactions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message