[
https://issues.apache.org/jira/browse/CASSANDRA-10070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163462#comment-15163462
]
Marcus Olsson commented on CASSANDRA-10070:
-------------------------------------------
For the basic implementation I think the tasks could be broken down as:
- Resource locking API & implementation
-- Maintenance scheduling API & basic repair scheduling
--- Rejection policy interface & default implementations
--- Configuration support
---- Table configuration
---- Global configuration (for pausing repairs in the basic implementation)
---- Node configuration
--- Aborting/interrupting repairs (Requires CASSANDRA-3486,CASSANDRA-11190)
---- Polling and monitoring module
---- Failure handling and retry
So that we start with the resource locking and then move on to the maintenance
scheduling API. And after that I think most tasks could be discussed in
parallel. Also I removed the task for management commands since I think it
would be easier to add them while implementing the features. WDYT?
> 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)
