cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Ortolani (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12166) Sequential repairs on LCS lead to many warnings
Date Mon, 11 Jul 2016 13:42:11 GMT

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

Stefano Ortolani updated CASSANDRA-12166:
-----------------------------------------
    Description: 
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}

Regards,
Stefano Ortolani

  was:
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}

Regards,
Stefano Ortolani


> 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
>            Priority: Minor
>
> 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}
> Regards,
> Stefano Ortolani



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

Mime
View raw message