cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-13786) Validation compactions can cause orphan sstable warnings
Date Tue, 22 Aug 2017 23:01:07 GMT
Blake Eggleston created CASSANDRA-13786:
-------------------------------------------

             Summary: Validation compactions can cause orphan sstable warnings
                 Key: CASSANDRA-13786
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13786
             Project: Cassandra
          Issue Type: Bug
            Reporter: Blake Eggleston
            Assignee: Blake Eggleston
            Priority: Minor
             Fix For: 4.0


I've seen LevelledCompactionStrategy occasionally logging: {quote}<sstable_name> from
level 0 is not on corresponding level in the leveled manifest. This is not a problem per se,
but may indicate an orphaned sstable due to a failed compaction not cleaned up properly."{quote}
warnings from a ValidationExecutor thread.

What's happening here is that a compaction running concurrently with the validation is promoting
(or demoting) sstables as part of an incremental repair, and an sstable has changed hands
by the time the validation compaction gets around to getting scanners for it. The sstable
isolation/synchronization done by validation compactions is a lot looser than normal compactions,
so seeing this happen isn't very surprising. Given that it's harmless, and not unexpected,
I think it would be best to not log these during validation compactions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message