cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10377) AssertionError: attempted to delete non-existing file CommitLog
Date Wed, 14 Oct 2015 16:59:06 GMT


Robert Stupp commented on CASSANDRA-10377:

[~vovodroid] & [~blambov], can you take a look at the 2.1 branch? It uses the same approach,
but is a bit different as this piece of code changed between 2.1 and 2.2.

> AssertionError: attempted to delete non-existing file CommitLog
> ---------------------------------------------------------------
>                 Key: CASSANDRA-10377
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: CentOS 7.1/x64
>            Reporter: Vovodroid
>            Assignee: Vovodroid
>            Priority: Critical
>         Attachments: 10377.patch
> After several hours of script tests (create and drop users, keyspaces and tables) exception
is thrown:
> {code}
> ERROR 02:58:39 Failed managing commit log segments. Commit disk failure policy is stop;
terminating thread
> java.lang.AssertionError: attempted to delete non-existing file CommitLog-5-1442599226756.log
> 	at ~[main/:na]
> 	at ~[main/:na]
> 	at org.apache.cassandra.db.commitlog.CommitLogSegment.discard(
> 	at org.apache.cassandra.db.commitlog.CommitLogSegmentManager$
> 	at org.apache.cassandra.db.commitlog.CommitLogSegmentManager$1.runMayThrow(
> 	at [main/:na]
> 	at [na:1.8.0_45]
> {code}
> I added some logs to *deleteWithConfirm* and it showed that this file really was deleted
by previous delete action, i.e. it was second attempt to delete the same log. Commit log with
next number exists in the same time, so log was switched.
> I disabled assert and it seems to have no no bad effect.

This message was sent by Atlassian JIRA

View raw message