You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matthew F. Dennis (JIRA)" <ji...@apache.org> on 2010/04/02 04:56:27 UTC

[jira] Updated: (CASSANDRA-930) make RR chance configurable

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

Matthew F. Dennis updated CASSANDRA-930:
----------------------------------------

    Attachment: CASSANDRA-930.patch

> make RR chance configurable
> ---------------------------
>
>                 Key: CASSANDRA-930
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-930
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.8
>
>         Attachments: CASSANDRA-930.patch
>
>
> Read load increases linearly with replication factor.  While this can be mitigated by simply adding machines, it would also be nice to be able to configure on a per-CF basis the chance of performing a read repair, so that particularly heavily read CFs could have a chance of (say) 10% and seldom-used ones could continue to repair every time, i.e., chance of 100%.  Thus, the "hot keys get repaired before waiting for anti-entropy to kick in" property gets preserved, but you might see a few more reads serving old values than before.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.