[
https://issues.apache.org/jira/browse/CASSANDRA-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054941#comment-13054941
]
Terje Marthinussen commented on CASSANDRA-2521:
-----------------------------------------------
Hm... there may actually be something here.
I am getting some *Compacted which does not seem to go away, not even after 7
hours after finished.
3 Compactions 2 of them have left 1 sstable, one has left 2.
I also happened to run 3 repairs, but one compaction starts just after one of
those repairs finished (the other 2 starts and finished during the repair.
This is running 2 as minimum compaction threshold.
The compaction which left 2 files, left them after a compaction of 3 files.
The 2 other *Compacted was made after compactions of 2 files
The system is under reasonably heavy input of data and sstables are added,
compacted and removed all the time. Just these which do not get removed and the
oldest is 8 hours now.
Note, I do not use mmap.
> Move away from Phantom References for Compaction/Memtable
> ---------------------------------------------------------
>
> Key: CASSANDRA-2521
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2521
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Chris Goffinet
> Assignee: Sylvain Lebresne
> Fix For: 1.0
>
> Attachments:
> 0001-Use-reference-counting-to-decide-when-a-sstable-can-.patch,
> 0001-Use-reference-counting-to-decide-when-a-sstable-can-v2.patch,
> 0002-Force-unmapping-files-before-deletion-v2.patch, 2521-v3.txt
>
>
> http://wiki.apache.org/cassandra/MemtableSSTable
> Let's move to using reference counting instead of relying on GC to be called
> in StorageService.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
