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

Lerh Chuan Low commented on CASSANDRA-8460:
-------------------------------------------

Bump! 

The branch has the latest updates I have (I've decided to go with a single CSM: 
https://github.com/apache/cassandra/compare/trunk...juiceblender:cassandra-8460-single-csm).
 I'm currently working my way through the unit tests, the weird thing is when 
run in isolation they work, when run together they fail, as if it's not being 
cleaned up properly. 

So far all the tests should work (as far as I can tell compared to 3.11) and I 
still have yet to add some tests for the archiving compaction. There are 
definitely a lot more things that require checking and I also haven't gotten 
round to checking what happens when you turn it off, etc. Just trying to get a 
lot of the compaction infrastructure to be aware that an archive directory 
exists and there's existing logic to actually perform the archiving compaction. 
I've also yet to test whether it's able to pick up compactions in the archive 
directory when there legitly exists compactions to be done in that directory. 

As before, comments welcome on this is going down the right path or not/is 
there a better way to do 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to