cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Meyer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10070) Automatic repair scheduling
Date Fri, 28 Aug 2015 13:06:47 GMT


Jim Meyer commented on CASSANDRA-10070:

+1 to including.  This feature would help with multi-tenancy and extend the idea of tunable
consistency since different use cases will have different repair requirements.  Individual
applications could self serve their repair frequency via the table properties instead of having
an administrator guess what frequency is needed.

It is a difficult and error prone chore for an application developer to devise a reliable
external mechanism for scheduling repairs.  It often ends up as a simple cron job that blindly
repairs all keyspaces once a day.

> 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