I don't have time to dive deep into the code of your version, but it may be ( https://issues.apache.org/jira/browse/CASSANDRA-13620 ) , or it may be something else.
I wouldn't expect compaction to touch them if they're invalid. The handle may be a leftover from trying to load them. On Tue, Aug 1, 2017 at 10:01 AM, Sotirios Delimanolis < sotodel...@yahoo.com.invalid> wrote: > @Jeff, why does compaction clear them and why does Cassandra keep a handle > to them? Shouldn't they be ignored entirely? Is there an error log I can > enable to detect them? > > @kurt, there are no such logs for any of these tables. We have a custom > log in our build of Cassandra that does shows that compactions are > happening for that table but only ever include the files from July. > > On Tuesday, August 1, 2017, 12:55:53 AM PDT, kurt greaves < > k...@instaclustr.com> wrote: > > > Seeing as there aren't even 100 SSTables in L2, LCS should be gradually > trying to compact L3 with L2. You could search the logs for "Adding > high-level (L3)" to check if this is happening. >
