hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5115) Make StorageID a UUID
Date Tue, 20 Aug 2013 20:50:53 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745399#comment-13745399

Arpit Agarwal commented on HDFS-5115:

Patch to allocate new Storage IDs as UUIDs. This solves the collision problem.

Leaving existing Storage IDs as they are. They will be changed to UUIDs when we handle DataNode
upgrades for HDFS-2832.

Post 2832 we could consider refactoring the type of the Storage ID from a String to a UUID
wherever referenced.
> Make StorageID a UUID
> ---------------------
>                 Key: HDFS-5115
>                 URL: https://issues.apache.org/jira/browse/HDFS-5115
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode
>    Affects Versions: 3.0.0
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>         Attachments: h5115.01.patch
> The Storage ID is currently generated from the DataNode's IP+Port+Random components.
This scheme will not work when we have separate Storage IDs for each storage directory as
there is a possibility of conflicts when an unreliable storage is intermittently offline.
> Converting it to a UUID makes collisions very unlikely.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message