[
https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124288#comment-13124288
]
Marcus Eriksson commented on CASSANDRA-2749:
--------------------------------------------
Anyone got a suggestion on how to do the available disk space checking? Reason
in that now we cannot simply check which dataFileLocation that has the most
available disk space, we need to check the subdirs where files are actually
written.
My naive first approach would be to simply change
DatabaseDescriptor.getDataFileLocationForTable(..) to take a column family
name, which we ought to always know when calling that method (and a quick check
seems to say that only compactions might prove a problem for this approach).
Comments?
> 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,
> 2749_backwards_compatible_v1.patch, 2749_backwards_compatible_v2.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
