[
https://issues.apache.org/jira/browse/CASSANDRA-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Podkowinski updated CASSANDRA-11427:
-------------------------------------------
Fix Version/s: 2.2.x
2.1.x
Status: Patch Available (was: In Progress)
> Range slice queries CL > ONE trigger read-repair of purgable tombstones
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-11427
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11427
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Fix For: 2.1.x, 2.2.x
>
> Attachments: 11427-2.1.patch
>
>
> Executing range queries (e.g. for reading token ranges) will compare the
> actual data instead of using digests when executed with CL > ONE. Responses
> will be consolidated by {{RangeSliceResponseResolver.Reducer}}, where the
> result of {{RowDataResolver.resolveSuperset}} is used as the reference
> version for the results. {{RowDataResolver.scheduleRepairs}} will then send
> the superset to all nodes that returned a different result before.
> Unfortunately this does also involve cases where the superset is just made up
> of purgable tombstone(s) that already have been compacted on the other nodes.
> In this case a read-repair will be triggered for transfering the purgable
> tombstones to all other nodes nodes that returned an empty result.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
