You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2015/07/29 07:54:06 UTC

[jira] [Commented] (CASSANDRA-8460) Make it possible to move non-compacting sstables to slow/big storage in DTCS

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

Jeff Jirsa commented on CASSANDRA-8460:
---------------------------------------

Pushed to https://github.com/jeffjirsa/cassandra/tree/cassandra-8460-2.2

1) Removed the time component of archive cutoff (no more archive_sstable_age_days), and refactored it to archive at max_sstable_age_days to match your original intent rather than projecting my own intentions
2) Reworked to explicitly shortcut and return if no archive disk is present
3) Created unit test (and fixed unit tests that this patch broke, primarily in DirectoriesTest)

[~krummas] - Can you review at your convenience? 

> Make it possible to move non-compacting sstables to slow/big storage in DTCS
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8460
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8460
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>            Assignee: Jeff Jirsa
>              Labels: dtcs
>             Fix For: 3.x
>
>
> It would be nice if we could configure DTCS to have a set of extra data directories where we move the sstables once they are older than max_sstable_age_days. 
> This would enable users to have a quick, small SSD for hot, new data, and big spinning disks for data that is rarely read and never compacted.



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