[
https://issues.apache.org/jira/browse/CASSANDRA-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170362#comment-13170362
]
Sylvain Lebresne commented on CASSANDRA-3635:
---------------------------------------------
bq. Since compaction throughput does not include validation anymore, I'd prefer
to default to something like 12/4 instead of effectively increasing the impact
of compaction + repair out of the box.
By default, if validation_throughput_mb_per_sec, validation are still included
with all compaction, so the default shouldn't change anything. The rational was
to 1) ease upgrade and 2) simplify configuration for people that don't care
about that. But now that I think of it, the fact that
compaction_throughput_mb_per_sec affects validation compaction only if the
validation specific setting is not set is probably a bit confusing. Maybe the
more natural way to do this is to have compaction_throughput_mb_per_sec be the
total maximum throughput for *all* compaction, and have 0 <=
validation_throughput_mb_per_sec <= compaction_throughput_mb_per_sec be a way
to further throttle validation compaction.
> Throttle validation separately from other compaction
> ----------------------------------------------------
>
> Key: CASSANDRA-3635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3635
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
