You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2015/04/06 03:00:13 UTC
[jira] [Commented] (CASSANDRA-9121) java.lang.AssertionError:
attempted to delete non-existing file
[ https://issues.apache.org/jira/browse/CASSANDRA-9121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14445937#comment-14445937 ]
Philip Thompson commented on CASSANDRA-9121:
--------------------------------------------
[~JoshuaMcKenzie] can confirm, but I believe this is a known windows issue.
> java.lang.AssertionError: attempted to delete non-existing file
> ---------------------------------------------------------------
>
> Key: CASSANDRA-9121
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9121
> Project: Cassandra
> Issue Type: Bug
> Environment: Windows 7
> Reporter: Will Zhang
> Fix For: 2.1.5
>
>
> upgraded from Cassandra 2.1.2 to 2.1.3 following the upgrade instructions. However, I started to see this new java.lang.AssertionError. See log below.
> Apart from this table listed below, this issue has also occurred on other user data tables. This error has not happened in the previous 2.1.2 version in our application (full 1 month of logs).
> Question also raised on Stackoverflow.
> http://stackoverflow.com/questions/29462267/cassandra-version-2-1-3-java-lang-assertionerror-attempted-to-delete-non-existi
> Environment: Windows 7 (yes I konw...), Java 1.8.0_11
> {code}
> ERROR [NonPeriodicTasks:1] 2015-04-05 20:34:39,638 CassandraDaemon.java:167 - Exception in thread Thread[NonPeriodicTasks:1,5,main]
> java.lang.AssertionError: attempted to delete non-existing file system-compaction_history-tmplink-ka-548-Data.db
> at org.apache.cassandra.io.util.FileUtils.deleteWithConfirm(FileUtils.java:126) ~[apache-cassandra-2.1.3.jar:2.1.3]
> at org.apache.cassandra.io.sstable.SSTableReader$Tidier$1.run(SSTableReader.java:2072) ~[apache-cassandra-2.1.3.jar:2.1.3]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_11]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_11]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[na:1.8.0_11]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[na:1.8.0_11]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_11]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_11]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)