cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13068) Fully expired sstable not dropped when running out of disk space
Date Wed, 21 Jun 2017 08:38:00 GMT

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

Marcus Eriksson updated CASSANDRA-13068:
----------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 3.11.x)
                       (was: 4.x)
                       (was: 3.0.x)
                   4.0
           Status: Resolved  (was: Patch Available)

I just realised that this breaks the public API on {{CompactionTask}} (someone might have
overridden the {{checkAvailableDiskSpace()}} or {{reduceScopeForLimitedSpace()}, this patch
would break that for them

Committed to trunk (4.0) only, thanks!

> Fully expired sstable not dropped when running out of disk space
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-13068
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13068
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction
>            Reporter: Marcus Eriksson
>            Assignee: Lerh Chuan Low
>              Labels: lhf
>             Fix For: 4.0
>
>
> If a fully expired sstable is larger than the remaining disk space we won't run the compaction
that can drop the sstable (ie, in our disk space check should not include the fully expired
sstables)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message