cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "C. Scott Andreas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12166) Sequential repairs on LCS lead to many warnings
Date Mon, 19 Nov 2018 02:23:01 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

C. Scott Andreas updated CASSANDRA-12166:
-----------------------------------------
    Component/s: Repair
                 Compaction

> 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: Compaction, Repair
>            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
(v7.6.3#76005)

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


Mime
View raw message