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 Wed, 20 Jan 2016 15:22:40 GMT


Marcus Olsson commented on CASSANDRA-10070:

I completely agree, I should create a document describing these things.

I've also thought about making a high level document for the whole proposal, so as to see
if everyone agrees that this is the way to go about the distributed scheduling. Then we can
take it from there and revise the proposal and hopefully later on break the JIRA into several
tasks to make it easier to review and develop this feature.

I think this document should contain:
* High level description of proposal (flow charts, etc.)
* Problems that could occur and possible solutions

Any thoughts or ideas on this?

> Automatic repair scheduling
> ---------------------------
>                 Key: CASSANDRA-10070
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Olsson
>            Assignee: Marcus Olsson
>            Priority: Minor
>             Fix For: 3.x
> 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