cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8635) STCS cold sstable omission does not handle overwrites without reads
Date Mon, 26 Jan 2015 17:28:34 GMT

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

Carl Yeksigian updated CASSANDRA-8635:
--------------------------------------
    Reviewer: Carl Yeksigian  (was: Tyler Hobbs)

> 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
>
>         Attachments: 0001-Include-cold-sstables-in-compactions-if-they-overlap.patch,
8635-v2.patch
>
>
> 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)

Mime
View raw message