You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2014/09/25 15:25:33 UTC
[jira] [Created] (CASSANDRA-8004) Run LCS for both repaired and
unrepaired data
Marcus Eriksson created CASSANDRA-8004:
------------------------------------------
Summary: Run LCS for both repaired and unrepaired data
Key: CASSANDRA-8004
URL: https://issues.apache.org/jira/browse/CASSANDRA-8004
Project: Cassandra
Issue Type: Bug
Reporter: Marcus Eriksson
Fix For: 2.1.1
If a user has leveled compaction configured, we should run that for both the unrepaired and the repaired data. I think this would make things a lot easier for end users
It would simplify migration to incremental repairs as well, if a user runs incremental repair on its nice leveled unrepaired data, we wont need to drop it all to L0, instead we can just start moving sstables from the unrepaired leveling straight into the repaired leveling
Idea could be to have two instances of LeveledCompactionStrategy and move sstables between the instances after an incremental repair run (and let LCS be totally oblivious to whether it handles repaired or unrepaired data). Same should probably apply to any compaction strategy, run two instances and remove all repaired/unrepaired logic from the strategy itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)