cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3635) Throttle validation separately from other compaction
Date Mon, 19 Dec 2011 09:48:30 GMT


Sylvain Lebresne commented on CASSANDRA-3635:

bq. Lets say we create a tree on A first after completion, we can create a tree on B and then
on C

In theory we kind of could. We do need to make sure trees are computed on roughly the same
data on all nodes, so we'll need to keep the flush at the same time, but then we don't have
to start the computation on all node right away. However, for that to work, we would need
to keep references on the sstables after the initial flush which adds it's sets of complication:
if for some reason a node never receive it's 'you can start computing your tree' message,
it will keep some sstables around forever. We can add a number of protection so that this
never happen, but still potentially a very nasty effect.

In any case, probably not a discussion related to this ticket.
> Throttle validation separately from other compaction
> ----------------------------------------------------
>                 Key: CASSANDRA-3635
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: repair
>             Fix For: 0.8.10, 1.0.7
>         Attachments: 0001-separate-validation-throttling.patch
> Validation compaction is fairly ressource intensive. It is possible to throttle it with
other compaction, but there is cases where you really want to throttle it rather aggressively
but don't necessarily want to have minor compactions throttled that much. The goal is to (optionally)
allow to set a separate throttling value for validation.
> PS: I'm not pretending this will solve every repair problem or anything. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message