[ 
https://issues.apache.org/jira/browse/CASSANDRA-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786556#action_12786556
 ] 

Jonathan Ellis edited comment on CASSANDRA-606 at 12/6/09 1:45 AM:
-------------------------------------------------------------------

+1 v2

      was (Author: jbellis):
    +1
  
> Compaction can't find files
> ---------------------------
>
>                 Key: CASSANDRA-606
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-606
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.5
>            Reporter: Chris Goffinet
>             Fix For: 0.5
>
>         Attachments: 
> 0001-ColumnFamily.onStart-was-not-checking-files-related-.patch, 
> 0001-v2-ColumnFamily.onStart-was-not-checking-files-related-.patch
>
>
> We have been seeing issues with compaction running very often. We ran into 
> this case when I found out in one of our CFs we were inserting a high volume 
> of columns. Our threshold for memtable size flushes is 64MB but the 
> MemtableObjectCountInMillions is 0.1 (we know this is low and will increase). 
> On average we are writing so much data that compaction kicks off reguarly. 
> And when we start trying to lookup data, we get lots of errors during 
> compaction and get_slice (since sometimes files don't get cleaned up). In 
> every event that this has occurred, a -Filter file was left behind. Never 
> Data or Index.
> ERROR [COMPACTION-POOL:1] 2009-12-05 15:04:47,412 
> DebuggableThreadPoolExecutor.java (line 120) Error in executor futuretask
> java.util.concurrent.ExecutionException: java.io.FileNotFoundException: 
> /mnt/var/cassandra/data/Digg/UserActivity-1243-Data.db (No such file or 
> directory)
>         at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
>         at java.util.concurrent.FutureTask.get(FutureTask.java:83)
>         at 
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.afterExecute(DebuggableThreadPoolExecutor.java:112)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:888)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:619)
> Caused by: java.io.FileNotFoundException: 
> /mnt/var/cassandra/data/Digg/UserActivity-1243-Data.db (No such file or 
> directory)
>         at java.io.RandomAccessFile.open(Native Method)
>         at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
>         at java.io.RandomAccessFile.<init>(RandomAccessFile.java:98)
>         at 
> org.apache.cassandra.io.BufferedRandomAccessFile.<init>(BufferedRandomAccessFile.java:142)
>         at 
> org.apache.cassandra.io.SSTableScanner.<init>(SSTableScanner.java:47)
>         at 
> org.apache.cassandra.io.SSTableReader.getScanner(SSTableReader.java:386)
>         at 
> org.apache.cassandra.io.CompactionIterator.getCollatingIterator(CompactionIterator.java:65)
>         at 
> org.apache.cassandra.io.CompactionIterator.<init>(CompactionIterator.java:48)
>         at 
> org.apache.cassandra.db.ColumnFamilyStore.doFileCompaction(ColumnFamilyStore.java:902)
>         at 
> org.apache.cassandra.db.ColumnFamilyStore.doFileCompaction(ColumnFamilyStore.java:861)
>         at 
> org.apache.cassandra.db.ColumnFamilyStore.doCompaction(ColumnFamilyStore.java:663)
>         at 
> org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:180)
>         at 
> org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:177)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         ... 2 more
>  INFO [main] 2009-12-05 15:08:54,384 SSTable.java (line 156) Deleted 
> /mnt/var/cassandra/data/Digg/UserActivity-1130-Data.db

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to