[
https://issues.apache.org/jira/browse/CASSANDRA-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170397#comment-13170397
]
Sylvain Lebresne commented on CASSANDRA-3635:
---------------------------------------------
I guess part of the idea is that validation is a bit cpu intensive (due to the
SHA-256 hash it does), so that allows to limit that too without being a problem
for other compaction. It also allows giving more room for ordinary compactions,
so that they complete earlier, which will impact reads (while having validation
finishing quickly is not necessarily as important).
> 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
