You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/09/20 22:30:56 UTC

[jira] [Resolved] (CASSANDRA-1817) Dynamic Read Repair

     [ https://issues.apache.org/jira/browse/CASSANDRA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-1817.
---------------------------------------

    Resolution: Later
    
> Dynamic Read Repair
> -------------------
>
>                 Key: CASSANDRA-1817
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1817
>             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
For more information on JIRA, see: http://www.atlassian.com/software/jira