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] [Updated] (CASSANDRA-5351) Avoid repairing already-repaired data by default
Date Thu, 14 Mar 2013 22:12:15 GMT

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

Jonathan Ellis updated CASSANDRA-5351:
--------------------------------------

    Description: 
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.

  was:
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.

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.

    
> 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.0
>
>
> 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

Mime
View raw message