[ 
https://issues.apache.org/jira/browse/CASSANDRA-13786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137691#comment-16137691
 ] 

Blake Eggleston commented on CASSANDRA-13786:
---------------------------------------------

Yeah for sure. It just seems like changing the interface is an oversize 
solution to the minor annoyance of getting periodic warnings in the logs. Maybe 
we don't need the log entry anymore, or it can be demoted to info, or there's a 
solution I haven't though of. That said, there probably aren't many 3rd party 
compaction strategies written against vanilla Cassandra these days.

> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to