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 Fri, 28 Aug 2015 08:48:47 GMT


Marcus Olsson commented on CASSANDRA-10070:

This is an optional feature in the way it's implemented, you can disable this and do only
manual/scripted repairs if you want. I think this is a fundamental functionality that should
be a part of the codebase, otherwise the same argument could be held against compactions,
those \*could\* also be handled in an external tool. Note that the actual repairs are always
handled inside of C* and that this is just a way to schedule them.

I think that data consistency management should be a part of a databases functionality. There
are already hints and read-repairs that are handled inside of C*, so why shouldn't repairs
be handled that way as well?

> Automatic repair scheduling
> ---------------------------
>                 Key: CASSANDRA-10070
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            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