cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2749) fine-grained control over data directories
Date Tue, 22 Nov 2011 16:02:40 GMT


Pavel Yaskevich commented on CASSANDRA-2749:

+1 first few additions:
 - You forgot to set `chmod +x ./bin/sstablemover`.
 - Good idea would be to use `mv` instead of `cp` when -d option is specified.

> fine-grained control over data directories
> ------------------------------------------
>                 Key: CASSANDRA-2749
>                 URL:
>             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,
0001-non-backwards-compatible-patch-for-2749-putting-cfs-.patch.gz, 2749.tar.gz, 2749_backwards_compatible_v1.patch,
2749_backwards_compatible_v2.patch, 2749_backwards_compatible_v3.patch, 2749_backwards_compatible_v4.patch,
2749_backwards_compatible_v4_rebase1.patch, 2749_not_backwards.tar.gz
> 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 (
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:!default.jspa
For more information on JIRA, see:


View raw message