cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-1817) Dynamic Read Repair
Date Tue, 15 May 2012 18:11:12 GMT


Jonathan Ellis updated CASSANDRA-1817:

    Priority: Minor  (was: Major)
      Labels: ponies  (was: )
> Dynamic Read Repair
> -------------------
>                 Key: CASSANDRA-1817
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stu Hood
>            Priority: Minor
>              Labels: ponies
> Read repair could (temporarily) adjust its own frequency (from the baseline) based on
the necessity of the repair for particular nodes. For example, a successful read repair (caused
data to be repaired) should bump the frequency for the node that needed repair, with the goal
that a node that has been offline for a while should trend toward 100% read repair while it
is successful.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message