Sorry about that Sotirios, I didn't make the connection between the two threads and this one dropped off my radar.
> Is it possible that there's always a compaction to be run in the > "repaired" state, with that many SSTables, that unrepaired compactions are > essentially "starved", considering the WrappingCompactionStrategy prioritizes > the "repaired" set? Not really as the code prioritises whichever pool has the most pending tasks. See here <https://github.com/apache/cassandra/blob/cassandra-2.2/src/java/org/apache/cassandra/db/compaction/WrappingCompactionStrategy.java#L76> Besides, the repaired pool will only increase if you actually run repairs, so there is only a limited set of data that can be compacted between repairs. Cassandra has been known to leave some file handles open on occasion, I assume you've restarted Cassandra to see if it clears out the files that are invalid (the ones that only have Data and Index)?
