[
https://issues.apache.org/jira/browse/CASSANDRA-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490486#comment-13490486
]
Sylvain Lebresne commented on CASSANDRA-4905:
---------------------------------------------
bq. I wonder if a expired column could create the digest of a tombstone if it
is timed out
This is already pretty much the case in practice. Expired columns are
transformed to tombstone at deserialization time, so repair will in fact get a
tombstone for any expired columns (unless the column expired between the
deserialization and it's use to compute the hash but that doesn't really
matter). But truth being told, as far as repair is concerned, it would be
better to never transform/consider an expired column as a tombstone, as one
node could see an expired column just before expiration while another could see
it after expiration, and the fact we do change them to tombstones means that in
that case repair will consider them inconsistent.
> 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
