[
https://issues.apache.org/jira/browse/CASSANDRA-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667738#comment-13667738
]
Michael Theroux commented on CASSANDRA-4905:
--------------------------------------------
One additional thought. It is possible that LeveledCompaction could make this
issue worse, because it is more efficient in deleting tombstones? It is more
efficient, but its not 100%, so is the chance that a tombstone was deleted on
one node, and not deleted on the other two nodes (in the case of a RF 3),
actually greater than SizeTiered? I guess it depends on a lot... just a
thought.
> 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
> Assignee: Sylvain Lebresne
> Fix For: 1.2.0 beta 3
>
> Attachments: 4905.txt
>
>
> 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
