I have a table that uses LeveledCompactionStrategy on Cassandra 2.2. At the moment, it has two SSTables, both in level 1, one that's repaired and one that isn't. $ sstablemetadata lb-135366-big-Data.db | head SSTable: /home/cassandra/data/my_keyspace/my_table/lb-135366-big Partitioner: org.apache.cassandra.dht.Murmur3Partitioner Bloom Filter FP chance: 0.100000 Minimum timestamp: 635879632038598571 Maximum timestamp: 636386914930971960 SSTable max local deletion time: 2147483647 Compression ratio: 0.3329089923791937 Estimated droppable tombstones: 0.04952060383516932 SSTable Level: 1 Repaired at: 1503094842214 $ sstablemetadata lb-135367-big-Data.db | head SSTable: /home/cassandra/data/my_keyspace/my_table/lb-135367-big Partitioner: org.apache.cassandra.dht.Murmur3Partitioner Bloom Filter FP chance: 0.100000 Minimum timestamp: 636386903663409770 Maximum timestamp: 636386932592309420 SSTable max local deletion time: 2147483647 Compression ratio: 0.34908682568154525 Estimated droppable tombstones: 0.4720670391061452 SSTable Level: 1 Repaired at: 0
What can I do to get these both into a repaired state? I tried running a full repair, but that didn't set the "Repaired at" state in the metadata and Cassandra still manages the SSTables separately as "repaired" and "unrepaired". I've never ran this cluster through the migration steps detailed here. Is that what's necessary in my case?
