[jira] [Updated] (CASSANDRA-4165) Generate Digest file for compressed SSTables
[ https://issues.apache.org/jira/browse/CASSANDRA-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-4165: --- Attachment: 0001-Generate-digest-for-compressed-files-as-well.patch > Generate Digest file for compressed SSTables > > > Key: CASSANDRA-4165 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4165 > Project: Cassandra > Issue Type: Improvement >Reporter: Marcus Eriksson >Priority: Minor > Attachments: 0001-Generate-digest-for-compressed-files-as-well.patch > > > We use the generated *Digest.sha1-files to verify backups, would be nice if > they were generated for compressed sstables as well. -- 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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: 2749_proper.tar.gz updated, of course mv should be used :) rebased as well > 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, > 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, > 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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: 2749_not_backwards.tar.gz updated; * sstablemover can now reverse changes (-r) and delete old files (-d). * LegacySSTableTest fixed, hopefully * added comments to cassandra.yaml > 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, > 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 > (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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: (was: 0001-non-backwards-compatible-patch-for-2749-putting-cfs-.patch.gz) > 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, > 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 > > > 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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: 0001-non-backwards-compatible-patch-for-2749-putting-cfs-.patch.gz > 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, > 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 > > > 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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: 0001-non-backwards-compatible-patch-for-2749-putting-cfs-.patch.gz ok, actually touched it again, a non-backwards compatible patch with a tool to move(copy) the files into subdirs script is in tools/sstablemover > 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, > 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 > > > 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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ 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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: 2749_backwards_compatible_v4_rebase1.patch rebased after 3464, renameSSTable code removed > 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_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
[jira] [Updated] (CASSANDRA-3464) Remove renameSSTables from ColumnFamilyStore.java
[ https://issues.apache.org/jira/browse/CASSANDRA-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-3464: --- Attachment: 0001-remove-dead-rename-sstable-code.patch > Remove renameSSTables from ColumnFamilyStore.java > - > > Key: CASSANDRA-3464 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3464 > Project: Cassandra > Issue Type: Improvement >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Trivial > Fix For: 1.1 > > Attachments: 0001-remove-dead-rename-sstable-code.patch > > > renameSSTables was only called by itself (via KeysIndex etc). This patch > removes the dead code. -- 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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: 2749_backwards_compatible_v4.patch v4 attached * renamed DatabaseDescriptor method * made file name checking case sensitive again... * removed unused rename code (following the renameSSTables call path, it looks very strange, even in trunk, ill fix this after this patch is merged) * cant figure out a way to make snapshotExists any better, im looking for a directory with the snapshot tag in all places, not sure if it could be wrong here (even if it is quite naive) * removed dead todos > 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_backwards_compatible_v1.patch, 2749_backwards_compatible_v2.patch, > 2749_backwards_compatible_v3.patch, 2749_backwards_compatible_v4.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
[jira] [Updated] (CASSANDRA-3414) Not possible to change row_cache_provider on existing cf
[ https://issues.apache.org/jira/browse/CASSANDRA-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-3414: --- Attachment: 3414.patch add the row_cache_provider to the avro record > Not possible to change row_cache_provider on existing cf > > > Key: CASSANDRA-3414 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3414 > Project: Cassandra > Issue Type: Bug >Affects Versions: 0.8.7 >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson > Fix For: 0.8.8 > > Attachments: 3414.patch > > > row_cache_provider is not possible to change using update column family xyz > with row_cache_provider='something' in 0.8 > It does work in 1.0.0 > Reason is that the field is not added to the avro record, patch attached > fixes that -- 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
[jira] [Updated] (CASSANDRA-3405) Row cache provider reported wrong in cassandra-cli
[ https://issues.apache.org/jira/browse/CASSANDRA-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-3405: --- Assignee: Marcus Eriksson > Row cache provider reported wrong in cassandra-cli > -- > > Key: CASSANDRA-3405 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3405 > Project: Cassandra > Issue Type: Bug > Components: Core >Affects Versions: 0.8.7 >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Minor > Attachments: 3405.patch > > > When doing "show schema;" in the CLI, the row_cache_provider is reported as > ConcurrentLinkedHashCacheProvider while it really is SerializingCacheProvider > Same goes for "describe keyspace" (after CASSANDRA-3384) on the 0.8 branch -- 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
[jira] [Updated] (CASSANDRA-3405) Row cache provider reported wrong in cassandra-cli
[ https://issues.apache.org/jira/browse/CASSANDRA-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-3405: --- Attachment: 3405.patch Trivial patch that adds the class name to the cfm thrift message > Row cache provider reported wrong in cassandra-cli > -- > > Key: CASSANDRA-3405 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3405 > Project: Cassandra > Issue Type: Bug > Components: Core >Affects Versions: 0.8.7 >Reporter: Marcus Eriksson >Priority: Minor > Attachments: 3405.patch > > > When doing "show schema;" in the CLI, the row_cache_provider is reported as > ConcurrentLinkedHashCacheProvider while it really is SerializingCacheProvider > Same goes for "describe keyspace" (after CASSANDRA-3384) on the 0.8 branch -- 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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: 2749_backwards_compatible_v3.patch third version, this is could be considered feature-complete, changes compared to v2 of the patch: * make sure disk space is calculated correctly - if there is a subdirectory in the datadirectory with the same name as the CF, check in that directory, otherwise, check in the datadirectory (the subdirectory will be created) * add config param * add test for RecursiveGlob * make RecursiveGlob ignore case when comparing file names * add test for scrubbing old style CFs to new style CFs (or, modify an existing test to check this too) > 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, > 2749_backwards_compatible_v3.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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: 2749_backwards_compatible_v2.patch Updated patch, working snapshots and incremental backups also a bit of cleanups btw, the patches are always against trunk, not against the older patches, is this the correct way to do it? > 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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-2749: --- Attachment: 2749_backwards_compatible_v1.patch First version of a backwards compatible patch. Approach is: * On startup, recursively glob all data directories to find existing sstables * whenever generating new files, look at the setting in the config, and put the file there * probably more, cant remember, my brain is messed up after fighting with this for a few days, look at patch! :) this gives that a user can enable/disable the setting without mocking around manually with the sstables. Comments? Yes, the setting is still hardcoded as a marker that this is not ready to be 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 >Priority: Minor > Fix For: 1.1 > > Attachments: > 0001-Make-it-possible-to-put-column-families-in-subdirect.patch, > 2749_backwards_compatible_v1.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
[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories
[ 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, //-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 //snapshots dir since the purpose of this patch is to make it possible to have the / 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
[jira] [Updated] (CASSANDRA-3263) Whitespace in SimpleSeedProvider string makes seed ignored
[ https://issues.apache.org/jira/browse/CASSANDRA-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-3263: --- Attachment: 3263.txt > Whitespace in SimpleSeedProvider string makes seed ignored > -- > > Key: CASSANDRA-3263 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3263 > Project: Cassandra > Issue Type: Bug > Components: Core >Affects Versions: 0.8.4, 0.8.5, 0.8.6 >Reporter: Marcus Eriksson >Priority: Minor > Fix For: 1.0.0 > > Attachments: 3263.txt > > > If a seeds given to SimpleSeedProvider contains whitespace, the seed will be > ignored > for example "1.2.3.4, 5.6.7.8" will only make 5.6.7.8 a seed. > patch simply trim()s the host. -- 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
