You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (JIRA)" <ji...@apache.org> on 2019/06/13 18:29:09 UTC
[jira] [Updated] (CASSANDRA-12166) Sequential repairs on LCS lead
to many warnings
[ https://issues.apache.org/jira/browse/CASSANDRA-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hanna updated CASSANDRA-12166:
-------------------------------------
Complexity: Low Hanging Fruit
> 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
> Components: Consistency/Repair, Local/Compaction
> Reporter: Stefano Ortolani
> Assignee: Paulo Motta
> Priority: Low
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org