[ 
https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175390#comment-13175390
 ] 

Pavel Yaskevich commented on CASSANDRA-2749:
--------------------------------------------

bq. I'm not sure I see what this one is. Are we talking of the migration 
process?

I was testing it like this : 

    # run 1.1 *without* modifications
    # ./tools/stress/bin/stress -n 50000 -S 512 -x KEYS
    # ./bin/nodetool -h localhost flush Keyspace1 Standard1
    # ./bin/nodetool -h localhost snapshot Keyspace1
    # made sure that Standard1.Idx-* SSTables are in the snapshots/<timestamp> 
directory
    # run 1.1 *with* you patch applied
    # checked if snapshots directory was moved and what files did it include - 
it was lucking Standard1.Idx-* files
    # cleaned data directory
    # repeated steps 1 - 5 but this time *with* your patch applied and it 
didn't include Standard1.Idx-* into snapshot

bq. Maybe it is more "natural" to have secondary indexes sstables be in the 
same directory than the base cfs? 

+1

                
> 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-2749.patch, 
> 0001-Make-it-possible-to-put-column-families-in-subdirect.patch, 
> 0001-non-backwards-compatible-patch-for-2749-putting-cfs-.patch.gz, 
> 0002-fix-unit-tests.patch, 0003-Fixes.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, 2749_not_backwards.tar.gz, 
> 2749_proper.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 
> (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

        

Reply via email to