[jira] [Comment Edited] (CASSANDRA-1983) Make sstable filenames contain a UUID instead of increasing integer
[ https://issues.apache.org/jira/browse/CASSANDRA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904441#comment-13904441 ] Daniel Shelepov edited comment on CASSANDRA-1983 at 2/18/14 8:14 PM: - OK, but symlinks are much easier to make unique, because they won't affect all that code that expects to find sstables under well-known names (regular names still being used in regular sstable storage). The fact that they're symlinks allows decoupling the problem from internal naming requirements. was (Author: daniels): OK, but distinct symlinks are much easier to make unique, because they won't affect all that code that expects to find sstables under well-known names (regular names still being used in regular sstable storage). The fact that they're symlinks allows decoupling the problem from internal naming requirements. Make sstable filenames contain a UUID instead of increasing integer --- Key: CASSANDRA-1983 URL: https://issues.apache.org/jira/browse/CASSANDRA-1983 Project: Cassandra Issue Type: Improvement Reporter: David King Priority: Minor sstable filenames look like CFName-1569-Index.db, containing an integer for uniqueness. This makes it possible (however unlikely) that the integer could overflow, which could be a problem. It also makes it difficult to collapse multiple nodes into a single one with rsync. I do this occasionally for testing: I'll copy our 20 node cluster into only 3 nodes by copying all of the data files and running cleanup; at present this requires a manual step of uniqifying the overlapping sstable names. If instead of an incrementing integer, it would be handy if these contained a UUID or somesuch that guarantees uniqueness across the cluster. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (CASSANDRA-1983) Make sstable filenames contain a UUID instead of increasing integer
[ https://issues.apache.org/jira/browse/CASSANDRA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904441#comment-13904441 ] Daniel Shelepov edited comment on CASSANDRA-1983 at 2/18/14 8:14 PM: - OK, but symlinks are much easier to make unique, because they won't affect all that code that expects to find sstables under well-known names (regular names still being available in regular sstable storage). The fact that they're symlinks allows decoupling the problem from internal naming requirements. was (Author: daniels): OK, but symlinks are much easier to make unique, because they won't affect all that code that expects to find sstables under well-known names (regular names still being used in regular sstable storage). The fact that they're symlinks allows decoupling the problem from internal naming requirements. Make sstable filenames contain a UUID instead of increasing integer --- Key: CASSANDRA-1983 URL: https://issues.apache.org/jira/browse/CASSANDRA-1983 Project: Cassandra Issue Type: Improvement Reporter: David King Priority: Minor sstable filenames look like CFName-1569-Index.db, containing an integer for uniqueness. This makes it possible (however unlikely) that the integer could overflow, which could be a problem. It also makes it difficult to collapse multiple nodes into a single one with rsync. I do this occasionally for testing: I'll copy our 20 node cluster into only 3 nodes by copying all of the data files and running cleanup; at present this requires a manual step of uniqifying the overlapping sstable names. If instead of an incrementing integer, it would be handy if these contained a UUID or somesuch that guarantees uniqueness across the cluster. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
