[
https://issues.apache.org/jira/browse/CASSANDRA-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436298#comment-17436298
]
Benedict Elliott Smith commented on CASSANDRA-17100:
----------------------------------------------------
I believe host_id is itself a UUID, so it can't really be used as a component
of a UUID :)
In essence, it will be smaller, in all likelihood an integer we increment by
one for each new node (and perhaps periodically re-use defunct values to avoid
accumulating extra bits to encode it). It will be used to guarantee uniqueness
of the TimeUUID we issue. Today we compute a per-launch (i.e. at process
startup) value by hashing various features of the JVM, but this doesn't provide
guarantees of uniqueness, so we can issue conflicting TimeUUID which would
break correctness.
We can replace host_id with these new values if we want, but this is probably
not particularly important.
> CEP-15: (C*) Unique Per-Node Id
> -------------------------------
>
> Key: CASSANDRA-17100
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17100
> Project: Cassandra
> Issue Type: Sub-task
> Components: Accord
> Reporter: Benedict Elliott Smith
> Priority: Normal
>
> Negotiate a unique and persistent id for each node on joining the cluster;
> use for TimeUUID and Ballot issuance
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
