[
https://issues.apache.org/jira/browse/CASSANDRA-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436302#comment-17436302
]
Benedict Elliott Smith edited comment on CASSANDRA-17100 at 10/30/21, 12:23 PM:
--------------------------------------------------------------------------------
I suppose we have an alternative option of correctly implementing the spec and
using MAC address for this purpose, and simply crashing the process on startup
if the MAC address conflicts with another node that's a member of the cluster
(which in most cases shouldn't be possible, if the nodes all reside on the same
network). In retrospect I'm not sure why we don't do this already.
was (Author: benedict):
I suppose we have an alternative option of correctly implementing the spec and
using MAC address for this purpose, and simply crashing the process on startup
if the MAC address conflicts with another node that's a member of the cluster.
> 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
> that is sufficiently compact to use for the node part of a v2, v6 or v8
> (Time)UUID, i.e. it should be at most 48 bits in length. In practice we
> should be able to target 7, 14 or 21 bits in length depending on cluster
> size, permitting more efficient vint encoding over the network and on disk.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
