cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11427) Range slice queries CL > ONE trigger read-repair of purgable tombstones
Date Wed, 30 Mar 2016 12:14:25 GMT

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

Stefan Podkowinski updated CASSANDRA-11427:
-------------------------------------------
    Attachment: 11427-2.1.patch

> 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
>         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)

Mime
View raw message