cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Theroux (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4905) Repair should exclude gcable tombstones from merkle-tree computation
Date Sun, 26 May 2013 18:02:21 GMT


Michael Theroux commented on CASSANDRA-4905:

The long compactions before the fix I think is a byproduct of leveled compaction.  I've seen
a number of people mention this on the users list.  Basically, leveled compaction in 1.1 is
a single threaded process, and increasing the compaction throughput doesn't help its rate.
 Leveled compaction is very slow to compact.

Leveled compaction should be better than Size Tiered, unless you are doing something like
major compactions (we are on some tables).

CASSANDRA-5398 looks interesting.  We rolled this fix + 1.1.11 into production this weekend.
 The last repair was a thing of beauty... finished in under 3 hours, very little streaming
and compaction... as it should be if you have don't have any, or very few inconsistencies
in your data. 
> Repair should exclude gcable tombstones from merkle-tree computation
> --------------------------------------------------------------------
>                 Key: CASSANDRA-4905
>                 URL:
>             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:

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:

View raw message