[
https://issues.apache.org/jira/browse/CASSANDRA-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414719#comment-16414719
]
Ben Slater commented on CASSANDRA-8460:
---------------------------------------
Think some more about this I think the other (and perhaps most important)
advantage of implementing in Cassandra is predictability for operators. It's
easy to say, for example, if I want data < 1 month old to be fast 1 need enough
fast disk space for that and I know it will be consistently fast after that I
need X disk space for the older data and I know it will be slower (and can even
clearly tell users that). Trying to tune performance of the hot data (and avoid
latency spikes) with with Cassandra + LVM sounds pretty hard.
> 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: Lerh Chuan Low
> 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: [email protected]
For additional commands, e-mail: [email protected]
