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

Stefan Podkowinski commented on CASSANDRA-12166:
------------------------------------------------

This also affects 2.1.15 with parallel repairs.

{noformat}
WARN  [ValidationExecutor:30] 2016-10-17 01:06:48,114 
LeveledCompactionStrategy.java:173 - Live sstable 
/cassandra/cass/live_01/documents/live_01-documents-ka-220901-Data.db 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.
INFO  [CompactionExecutor:3307] 2016-10-17 01:06:48,117 CompactionTask.java:274 
- Compacted 2 sstables to 
[/cassandra/cass/live_01/documents/live_01-documents-ka-220901,].  53,981,803 
bytes to 53,982,189 (~100% of original) in 3,517ms = 14.637881MB/s.  38,069 
total partitions merged to 38,068.  Partition merge counts were {1:38067, 2:1, }
{noformat}

> Sequential repairs on LCS lead to many warnings
> -----------------------------------------------
>
>                 Key: CASSANDRA-12166
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12166
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stefano Ortolani
>            Assignee: Paulo Motta
>            Priority: Minor
>              Labels: lcs, lhf
>
> I have been testing sequential repairs on 3.0.8 and now the logs are filled 
> with the following warnings. Note that they do make sense since snapshotting 
> is part of the repair process if sequential, but I was wondering if this 
> level of verbosity was intended.
> {noformat}
> WARN  [ValidationExecutor:3] 2016-07-11 13:35:52,930 
> LeveledCompactionStrategy.java:231 - Live sstable 
> /data/cassandra/data/schema/cf-e06f37a010bc11e6bb236776bf484396/snapshots/acc9a360-476a-11e6-87e0-dbcbe81a0cea/mb-840-big-Data.db
>  
> 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.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to