cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3314) Fail to delete -Index files if index is currently building
Date Mon, 17 Oct 2011 17:50:10 GMT

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

Jonathan Ellis updated CASSANDRA-3314:
--------------------------------------

    Attachment: 0002-fix.patch
                0001-cleanup.patch

01 does some cleanup around index building, including adding docstrings to make clear when
references need to be acquired on sstables involved.

02 adds the missing reference acquisitions for new index creation and loadNewSSTables.
                
> Fail to delete -Index files if index is currently building
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-3314
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3314
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Radim Kolar
>            Assignee: Jonathan Ellis
>            Priority: Minor
>              Labels: compaction, indexing
>             Fix For: 1.0.1
>
>         Attachments: 0001-cleanup.patch, 0002-fix.patch
>
>
> If there is index building in progress, following errors are thrown if cassandra is trying
to delete *-Index.db files. There is no problem with deleting -Data or -Filter.. files. CF
is using leveled compaction but it is probably not related.
> ERROR [NonPeriodicTasks:1] 2011-10-05 09:13:03,702 AbstractCassandraDaemon.java
> (line 133) Fatal exception in thread Thread[NonPeriodicTasks:1,5,main]
> java.lang.RuntimeException: java.io.IOException: Failed to delete C:\var\lib\cas
> sandra\data\test\sipdb-h-772-Index.db
>         at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:3
> 4)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:44
> 1)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> access$301(ScheduledThreadPoolExecutor.java:98)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> run(ScheduledThreadPoolExecutor.java:206)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:908)
>         at java.lang.Thread.run(Thread.java:662)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message