[
https://issues.apache.org/jira/browse/CASSANDRA-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517629#comment-16517629
]
Aleksey Yeschenko commented on CASSANDRA-14515:
-----------------------------------------------
[3.11 branch|https://github.com/iamaleksey/cassandra/commits/14515-3.11] and
[4.0 branch|https://github.com/iamaleksey/cassandra/commits/14515-4.0].
CI
[here|https://circleci.com/workflow-run/98c78715-3725-422f-99c3-81fa4e199666],
[here|https://circleci.com/workflow-run/ead96ef6-1d10-4d39-af0b-16a656add658],
and
[here|https://circleci.com/workflow-run/cce784b8-3131-48b5-aa0d-a3be98cc9741].
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
