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/09/27 21:27:08 UTC

[jira] [Comment Edited] (CASSANDRA-5515) Track sstable coldness

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

Tyler Hobbs edited comment on CASSANDRA-5515 at 9/27/13 7:26 PM:
-----------------------------------------------------------------

5515-2.0-v2.txt moves the row clearing to SSTableDeletingTask, increments reads in CollationController, and uses Keyspace.SYSTEM_KS.

With regards to restoring from snapshots, I think the actual restore procedure might be somewhat complicated and of relatively little benefit compared to the current patch.  Mind if we move that to another ticket?
                
      was (Author: thobbs):
    5515-2.0-v2.txt moves the row clearing to SSTableDeletingTask, increments reads in CollationController, and uses Keyspace.SYSTEM_KS.

With regards to restoring from snapshots, I think the actual restore procedure might be somewhat complicated and of relatively little benefit compare to the current patch.  Mind if we move that to another ticket?
                  
> Track sstable coldness
> ----------------------
>
>                 Key: CASSANDRA-5515
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5515
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Tyler Hobbs
>             Fix For: 2.0.2
>
>         Attachments: 0001-Track-row-read-counts-in-SSTR.patch, 5515-2.0-v1.txt, 5515-2.0-v2.txt
>
>
> Keeping a count of reads per-sstable would allow STCS to automatically ignore cold data rather than recompacting it constantly with hot data, dramatically reducing compaction load for typical time series applications and others with time-correlated access patterns.  We would not need a separate age-tiered compaction strategy.
> (This will really be useful in conjunction with CASSANDRA-5514.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira