ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chaouki Dhib (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-9499) Node IDs are not guaranteed to be unique after reboot
Date Fri, 07 Sep 2018 14:38:00 GMT
Chaouki Dhib created IGNITE-9499:
------------------------------------

             Summary: Node IDs are not guaranteed to be unique after reboot
                 Key: IGNITE-9499
                 URL: https://issues.apache.org/jira/browse/IGNITE-9499
             Project: Ignite
          Issue Type: Bug
            Reporter: Chaouki Dhib


Ignite uses the JDK's UUID.randomUUID() method to generated a UUID as the the node id. This
method generates UUID of variant 2 and of version 4. The version 4 is just a randomly generated
ID. Therefore, there is no guarantee that after a reboot, a node will have not the same ID
as before. The probably of this happening is extremely small [1], but the fact is, the current
implementation is non-deterministic. The problem can easily be fixed by using a UUID of version
1 (that makes use of a timestamp and of the node's MAC address) [2].


[1] Cf [https://en.wikipedia.org/wiki/Universally_unique_identifier#Collisions]

[2] [https://github.com/cowtowncoder/java-uuid-generator] provides such fonctioanlity.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message