cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-1983) Make sstable filenames contain a UUID instead of increasing integer
Date Tue, 18 Feb 2014 17:46:27 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-1983.
---------------------------------------

    Resolution: Won't Fix

"The only extra piece of code would be creating and tearing down symlinks when real sstables
are created and deleted."

That doesn't really buy us anything for the "I want to merge in some sstables from an external
source" problem though; just changes the constraint from "distinct filenames" to "distinct
symlink names."

Created CASSANDRA-6719 to supersede this.

> 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)

Mime
View raw message