cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David King (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1983) Make sstable filenames contain a UUID instead of increasing integer
Date Thu, 13 Jan 2011 22:06:46 GMT

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

David King commented on CASSANDRA-1983:
---------------------------------------

As long as the host is still willing to read filenames without its own uuid, sure

> 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
>          Components: Core
>    Affects Versions: 0.7.0
>            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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message