[
https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-2749:
---------------------------------------
Attachment: 2749.tar.gz
4 patches, one is the same as the v4, the other three patches are
* change configuration option name
* make LegacySSTable test work by telling Descriptor that the file is old-style
* make incremental backups work
- problem was when migrating from old-style to new-style, the
generation-counter in ColumnFamilyStore generated clashing ids, which was not a
problem until it tried to hard link the files to the same directory with the
same name. This should be refactored in CASSANDRA-1983 (i'll give that a try
when this is merged)
> 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
> Assignee: Marcus Eriksson
> Priority: Minor
> Fix For: 1.1
>
> Attachments:
> 0001-Make-it-possible-to-put-column-families-in-subdirect.patch, 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
>
>
> 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
