cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-14515) Short read protection in presence of almost-purgeable range tombstones may cause permanent data loss
Date Wed, 20 Jun 2018 14:47:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518212#comment-16518212
] 

Sam Tunnicliffe commented on CASSANDRA-14515:
---------------------------------------------

+1 LGTM too. Tests do look good - there's 1 failure in a semi-relevant dtest ({{consistency_test.py::TestConsistency::test_short_read}}
on the 3.11 branch), but I've verified it's unrelated to this patch.

> Short read protection in presence of almost-purgeable range tombstones may cause permanent
data loss
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14515
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14515
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>            Priority: Blocker
>             Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> Because read responses don't necessarily close their open RT bounds, it's possible to
lose data during short read protection, if a closing bound is compacted away between two adjacent
reads from a node.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message