You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2013/10/05 00:17:42 UTC

[jira] [Updated] (CASSANDRA-6109) Consider coldness in STCS compaction

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

Tyler Hobbs updated CASSANDRA-6109:
-----------------------------------

    Attachment: 6109-v1.patch

6109-v1.patch (and [branch|https://github.com/thobbs/cassandra/tree/CASSANDRA-6109]) picks the hottest sstables for buckets, ignores relatively cold sstables, and then picks the hottest overall bucket.  I agree about scope creep, so no changes were made to the compaction manager queue.

> Consider coldness in STCS compaction
> ------------------------------------
>
>                 Key: CASSANDRA-6109
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6109
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Tyler Hobbs
>             Fix For: 2.0.2
>
>         Attachments: 6109-v1.patch
>
>
> I see two options:
> # Don't compact cold sstables at all
> # Compact cold sstables only if there is nothing more important to compact
> The latter is better if you have cold data that may become hot again...  but it's confusing if you have a workload such that you can't keep up with *all* compaction, but you can keep up with hot sstable.  (Compaction backlog stat becomes useless since we fall increasingly behind.)



--
This message was sent by Atlassian JIRA
(v6.1#6144)