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/08/09 21:17:51 UTC
[jira] [Comment Edited] (CASSANDRA-5351) Avoid repairing
already-repaired data by default
[ https://issues.apache.org/jira/browse/CASSANDRA-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735160#comment-13735160 ]
Jonathan Ellis edited comment on CASSANDRA-5351 at 8/9/13 7:17 PM:
-------------------------------------------------------------------
bq. Given our setup we would need to repair once a day which wouldn't fly
Given the tiny amounts of data being repaired, I think you could get down to hourly.
But, the more often you repair the less big a full "separate set of levels for unrepaired data" would be. So maybe that's the way to go.
was (Author: jbellis):
bq. Given our setup we would need to repair once a day which wouldn't fly
Given the tiny amounts of data being repaired, I think you could get down to hourly.
> Avoid repairing already-repaired data by default
> ------------------------------------------------
>
> Key: CASSANDRA-5351
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5351
> Project: Cassandra
> Issue Type: Task
> Components: Core
> Reporter: Jonathan Ellis
> Labels: repair
> Fix For: 2.1
>
>
> Repair has always built its merkle tree from all the data in a columnfamily, which is guaranteed to work but is inefficient.
> We can improve this by remembering which sstables have already been successfully repaired, and only repairing sstables new since the last repair. (This automatically makes CASSANDRA-3362 much less of a problem too.)
> The tricky part is, compaction will (if not taught otherwise) mix repaired data together with non-repaired. So we should segregate unrepaired sstables from the repaired ones.
--
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