[
https://issues.apache.org/jira/browse/CASSANDRA-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336502#comment-16336502
]
Lerh Chuan Low commented on CASSANDRA-8460:
-------------------------------------------
[~pavel.trukhanov] That's a really good question. I can't think of any reason
why other than it just being a relic of my thoughts from JBOD/making sure
unrepaired/repaired/pending repaired SSTables stay in different disks...so if
the user wanted to replace just the cold archive disk they could do so. Though
I'm not sure if having a separate CS actually allows that. Hmm...
I guess it may become clearer to me as I dive into the code, but thank you for
pointing it out :)
> 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
> Priority: Major
> Labels: doc-impacting, dtcs
> Fix For: 4.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
