[
https://issues.apache.org/jira/browse/CASSANDRA-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518250#comment-16518250
]
Aleksey Yeschenko commented on CASSANDRA-14515:
-----------------------------------------------
Thanks guys. Committed to 3.0 as
[4e23c9e4dba6ee772531d82980f73234bd41869a|https://github.com/apache/cassandra/commit/4e23c9e4dba6ee772531d82980f73234bd41869a]
and merged upwards.
The nits you both had (offline) were addressed on commit.
> 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: 4.0, 3.0.17, 3.11.3
>
>
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
