cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lerh Chuan Low (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13068) Fully expired sstable not dropped when running out of disk space
Date Tue, 30 May 2017 02:27:04 GMT

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

Lerh Chuan Low commented on CASSANDRA-13068:
--------------------------------------------

Thanks for the quick reply. I'll look into writing some tests (I was initially wondering how
that would be done without actually filling up the disk of the machine). I didn't know about
Byteman, so going to do some digging into it and also thanks for providing an example. 

Re: {{Sets.difference}} - you're right, just checked the java doc. Wasn't aware it returned
an unmodifiable view of a set. 

> 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: 3.0.x, 3.11.x, 4.x
>
>
> 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.3.15#6346)

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


Mime
View raw message