cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2404) if out of disk space reclaim compacted SSTables during memtable flush
Date Thu, 31 Mar 2011 10:23:05 GMT

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

Stu Hood commented on CASSANDRA-2404:
-------------------------------------

Actually, I would be all for _moving_ the logic from getDataFileLocation to createFlushWriter...
not having room to flush is much more urgent than not having room to compact, and as a node
gets closer to full, large bucket compactions will begin to spam GC for compactions that aren't
going to be possible anyway.

> if out of disk space reclaim compacted SSTables during memtable flush
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-2404
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2404
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7.4
>            Reporter: Aaron Morton
>            Assignee: Aaron Morton
>            Priority: Minor
>             Fix For: 0.7.5
>
>
> During compaction if there is not enough disk space we invoke GC to reclaim unused space.
> During memtable and binary memtable flush we just error out if there is not enough disk
space to flush the table. 
> Can we make cfs.createFlushWriter() use the same logic as Table.getDataFileLocation()
to reclaim space if needed?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message