cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Spriegel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4905) Repair should exclude gcable tombstones from merkle-tree computation
Date Sat, 03 Nov 2012 21:31:11 GMT

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

Christian Spriegel commented on CASSANDRA-4905:
-----------------------------------------------

Also I wonder if a expired column could create the digest of a tombstone if it is timed out.

If a gcable tombstone does not alter the digest, then a timed-out ExpiredColumn should behave
like a tombstone.
                
> Repair should exclude gcable tombstones from merkle-tree computation
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-4905
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4905
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Christian Spriegel
>
> Currently gcable tombstones get repaired if some replicas compacted already, but some
are not compacted.
> This could be avoided by ignoring all gcable tombstones during merkle tree calculation.
> This was discussed with Sylvain on the mailing list:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/repair-compaction-and-tombstone-rows-td7583481.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message