[
https://issues.apache.org/jira/browse/CASSANDRA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974542#action_12974542
]
Jonathan Ellis commented on CASSANDRA-1817:
-------------------------------------------
This could have a large impact on performance, though, and for a non-random
workload you'd still be repairing the hot rows over and over.
I kind of think that for workloads where RR < 1.0 makes sense, it makes sense
even when actual repairs are happening.
> 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
> Fix For: 0.7.1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
