[
https://issues.apache.org/jira/browse/CASSANDRA-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2404:
--------------------------------------
Affects Version/s: (was: 0.7.4)
Assignee: Jonathan Ellis (was: Aaron Morton)
The reason we didn't do this historically is we didn't know how much free space
should be the Panic Threshold on flush, whereas compaction has an
easy-to-compute upper bound. Now we we can compute the flush size very easily
(basically the throughput value + 2xkey sizes) so we can run the same "if not
enough room then attempt a GC" logic.
> 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
> Reporter: Aaron Morton
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.6
>
>
> 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
