[
https://issues.apache.org/jira/browse/CASSANDRA-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789939#comment-13789939
]
Jonathan Ellis commented on CASSANDRA-6109:
-------------------------------------------
Sorry, I had to bikeshed just a little more. Looks like it's cleaner to
restrict prepBuckets (renamed) to restricting by max sstables + coldness, and
let mostInteresting take care of dropping too-small buckets. This means we'll
do a small amount of unnecessary sorting-by-coldness but this is negligible
compared to the actual compaction we're setting up.
Pushed to https://github.com/jbellis/cassandra/commits/6109
> 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, 6109-v2.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)
