cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4124) staggered repair for multiple ranges
Date Tue, 26 Jun 2012 20:12:44 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401660#comment-13401660
] 

Jonathan Ellis commented on CASSANDRA-4124:
-------------------------------------------

Now that we support repairing a specific range of data (CASSANDRA-3912),  you could expose
"repair one vnode's worth of data" easily enough through nodetool, no changes needed on the
backend.
                
> staggered repair for multiple ranges
> ------------------------------------
>
>                 Key: CASSANDRA-4124
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4124
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Sam Overton
>            Assignee: Sam Overton
>
> One difference to take into account when considering the benefit of staggering repair:
with the introduction of a distribution factor, replicas for all ranges on one host will be
spread across a larger number of other hosts (DF > RF), so the impact of repair will be
less with larger values of DF.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message