You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Marton Elek (Jira)" <ji...@apache.org> on 2020/06/02 15:41:00 UTC
[jira] [Commented] (HDDS-3707) UUID can be non unique for a huge
samples
[ https://issues.apache.org/jira/browse/HDDS-3707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123943#comment-17123943 ]
Marton Elek commented on HDDS-3707:
-----------------------------------
Thanks to open this [~maobaolong]. I am trying to understand the risk here, but to have the same datanodeId and pipelineId seems to have only a very low chance. I expect 10-90 thousands of datanodeId/containerId, I think the chance for the collision is very-very low.
What is your suggestion, what should be used instead of UUID?
> UUID can be non unique for a huge samples
> -----------------------------------------
>
> Key: HDDS-3707
> URL: https://issues.apache.org/jira/browse/HDDS-3707
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: om, Ozone Datanode, SCM
> Affects Versions: 0.7.0
> Reporter: maobaolong
> Priority: Minor
>
> Now, we have used UUID as id for many places, for example, DataNodeId, pipelineId. I believe that it should be pretty less chance to met collision, but, if met the collision, we are in trouble.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org