[
https://issues.apache.org/jira/browse/CASSANDRA-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170490#comment-13170490
]
Vijay commented on CASSANDRA-3635:
----------------------------------
Nope, I think we can create a tree independent on the nodes and then compare it
Lets say we create a tree on A first after completion, we can create a tree on
B and then on C (We have to sync on time, may be flush at the time when the
repair was requested or something like that).
Once we have all the 3 Trees we can compare and transfer which as required.
Once we have all the trees we can exchange the trees and then start real
streaming if needed. That way we dont bring the whole range down or hot.
> 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
