You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2015/01/21 00:04:35 UTC

[jira] [Commented] (CASSANDRA-8635) STCS cold sstable omission does not handle overwrites without reads

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

T Jake Luciani commented on CASSANDRA-8635:
-------------------------------------------

Will this fix take many days? if so we might want to wait till 2.1.4 since there is a workaround

> STCS cold sstable omission does not handle overwrites without reads
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-8635
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8635
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Marcus Eriksson
>            Priority: Critical
>             Fix For: 2.1.3
>
>
> In 2.1, STCS may omit cold SSTables from compaction (CASSANDRA-6109).  If data is regularly overwritten or deleted (but not enough to trigger a single-sstable tombstone purging compaction), data size on disk may continuously grow if:
> * The table receives very few reads
> * The reads only touch the newest SSTables
> Basically, if the overwritten data is never read and there aren't many tombstones, STCS has no incentive to compact the sstables.  We should take sstable overlap into consideration as well as coldness to address this case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)