cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7925) TimeUUID LSB should be unique per process, not just per machine
Date Fri, 22 May 2015 07:10:17 GMT

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

Benedict commented on CASSANDRA-7925:
-------------------------------------

I'm not sure we need each thread to have its own... If a client or another server generates
a UUID, they should both provide the LSB themselves. If this server generates one, the act
is synchronized to ensure no duplication.

I think salting clockSeqAndNode with the ClassLoader.hashCode() and PID should be sufficient?


> TimeUUID LSB should be unique per process, not just per machine
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-7925
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7925
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Peter M├Ądel
>            Assignee: T Jake Luciani
>             Fix For: 2.2.x
>
>         Attachments: cassandra-uuidgen.patch
>
>
> as pointed out in [CASSANDRA-7919|https://issues.apache.org/jira/browse/CASSANDRA-7919?focusedCommentId=14132529&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14132529]
lsb collisions are also possible serverside.
> a sufficient solution would be to include references to pid and classloader within lsb.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message