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

["Jeff Jirsa (JIRA)" <ji...@apache.org>]

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

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

[~krummas] Does it make sense to address this in a few parts? 

1) Create a new notion of tiered storage configurable per node in yaml (either one default tier for hot data {{data_file_directories}} and one tier for cold data {{archive_file_directories}}, or some form of arbitrary named tiers? )
2) Allow compaction strategies access to the various tiers with CASSANDRA-8671 ( tagging [~bdeggleston] for visibility )
3) Extend DTCS to take advantage of CASSANDRA-8671 + slow tier from step 1 as a compaction option such as {{WITH compaction = {'class': 'DateTieredCompactionStrategy', 'timestamp_resolution':'<resolution>', 'base_time_seconds':'3600', 'max_sstable_age_days':'7', 'max_sstable_age_disk_tier':'archive' }; }} ? 



> 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
>
> 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)