cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Olsson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10070) Automatic repair scheduling
Date Tue, 23 Feb 2016 17:48:18 GMT


Marcus Olsson commented on CASSANDRA-10070:

bq. Sounds good! We could ask the user to pause, but I think doing that automatically via
"system interrupts" is better. It just ocurred to me that both "the pause" or "system interrupts"
will prevent new repairs from starting, but what about already running repairs? We will probably
want to interrupt already running repairs as well in some situations. For this reason CASSANDRA-3486
is also relevant for this ticket (adding it as a dependency of this ticket).

bq. Then I think we should either have timeout, or add an ability to cancel/interrupt a running
scheduled repair in the initial version, to avoid hanging repairs to render the automatic
repair scheduling useless.
I think the timeout would be good enough in the initial version. I guess the interruption
of repairs would be handled by CASSANDRA-3486? Perhaps it would be possible to extend that
feature later to be able to cancel a scheduled repair? Here I'm thinking that the interruption
is stopping the running repair and allowing the scheduled job to retry it immediately, while
cancelling it would prevent the scheduled job from retrying it immediately.

bq. WDYT? Feel free to update or break-up into smaller or larger subtasks, and then create
the actual subtasks to start work on them.
Sounds good, I'll have a closer look on the subtasks tomorrow! I guess we will have sort of
a dependency tree for some of the tasks.

> Automatic repair scheduling
> ---------------------------
>                 Key: CASSANDRA-10070
>                 URL:
>             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

View raw message