[
https://issues.apache.org/jira/browse/CASSANDRA-10070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132680#comment-15132680
]
Yuki Morishita commented on CASSANDRA-10070:
--------------------------------------------
[~molsson] Thanks for the write up. I have couple of questions:
* What would "lock resource" be like for repair scheduling? I think the value
controls number of repair jobs running at given time in the whole cluster, and
we don't want to run as many repair jobs at once.
* It seems the scheduling only makes sense for repairing primary range of the
node ('nodetool -pr') since we end up repairing all nodes eventually. Are you
considering other options like subrange ('nodetool -st -et') repair?
> Automatic repair scheduling
> ---------------------------
>
> Key: CASSANDRA-10070
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10070
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Olsson
> Assignee: Marcus Olsson
> Priority: Minor
> Fix For: 3.x
>
> Attachments: Distributed Repair Scheduling.doc
>
>
> Scheduling and running repairs in a Cassandra cluster is most often a
> required task, but this can both be hard for new users and it also requires a
> bit of manual configuration. There are good tools out there that can be used
> to simplify things, but wouldn't this be a good feature to have inside of
> Cassandra? To automatically schedule and run repairs, so that when you start
> up your cluster it basically maintains itself in terms of normal
> anti-entropy, with the possibility for manual configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
