[
https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118696#comment-13118696
]
Marcus Eriksson commented on CASSANDRA-2749:
--------------------------------------------
It is not backwards compatible, i figured it was not worth the extra
complexity, i imagine the "upgrade"-path to be:
1. shut down node
2. edit config file
3. symlink in SSDs and move the files into the subdirectories
4. start node
Of course, this could be done on startup by cassandra itself, but providing a
shell-script that does it keeps it simple, what do you think? I really dont
want the complexity with sstable files in two places at the same time.
My solution simply changed the Descriptor class to return paths to sstable
files in subdirs, and then fix everything that was affected. Many of the
classes modified were due to assumptions in the unit tests. I'm currently
refactoring the Descriptor class to make it cleaner and a central place to glob
for files etc. Expect a patch tonight or tomorrow.
I will of course change DatabaseDescriptor.getPerCFDirectory() to read the
config file, kept it hard coded to make testing simpler.
> fine-grained control over data directories
> ------------------------------------------
>
> Key: CASSANDRA-2749
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2749
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Priority: Minor
> Fix For: 1.1
>
> Attachments:
> 0001-Make-it-possible-to-put-column-families-in-subdirect.patch
>
>
> Currently Cassandra supports multiple data directories but no way to control
> what sstables are placed where. Particularly for systems with mixed SSDs and
> rotational disks, it would be nice to pin frequently accessed columnfamilies
> to the SSDs.
> Postgresql does this with tablespaces
> (http://www.postgresql.org/docs/9.0/static/manage-ag-tablespaces.html) but we
> should probably avoid using that name because of confusing similarity to
> "keyspaces."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
