[
https://issues.apache.org/jira/browse/CASSANDRA-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373922#comment-16373922
]
Lerh Chuan Low commented on CASSANDRA-8460:
-------------------------------------------
Hi Jon,
Thanks for pitching in :)
Maybe you have stumbled upon the case where data has been resurrected in JBOD
configuration in your experiences...? In theory since splitting by token range
there should be no more such cases. It is safe.
That said, I have not heard of lvmcache so I'll go and have a look at it. I do
agree that this as it is introduces a lot of code branches and complexity and
simple is a feature, which is why I was seeking feedback and becoming
wary...this sounds good - readily available, works for every CS and doesn't
introduce all that complexity. I'll test it.
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
