[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories

["Marcus Eriksson (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-2749:
---------------------------------------

    Attachment: 0001-Make-it-possible-to-put-column-families-in-subdirect.patch

submitting a "working" patch for separating column families into subdirectories, <ks>/<cf>/<cf>-xyz.db

There are alot of things to clean up/refactor, but submitting patch for comments.

Unit tests work both for new-style dirs and old (except for a backup test that i will fix when backups actually end up where they should).

TODO: (probably more than this)
- snapshots need to go into the <ks>/<cf>/snapshots dir since the purpose of this patch is to make it possible to have the <cf>/ directory on a separate drive
- incremental backups - same issue as for snapshots
- refactoring of Descriptor class, quite hairy now
- Disk space checking in column family subdirs
                
> 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
>         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