hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5232) Protocol changes to transmit StorageUuid
Date Thu, 19 Sep 2013 20:23:53 GMT

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

Tsz Wo (Nicholas), SZE commented on HDFS-5232:
----------------------------------------------

- GetAdditionalDatanodeRequestProto.existingStorageIDs was committed only to the HDFS-2832
branch.  We may rename it directly without deprecation.
- Even for other cases like DatanodeStorageProto.storageID, we could rename it without deprecation
since renaming a variable does not change the wire byte format.  It does break programs compiled
with the generated code but it is not something we need to avoid.
                
> Protocol changes to transmit StorageUuid
> ----------------------------------------
>
>                 Key: HDFS-5232
>                 URL: https://issues.apache.org/jira/browse/HDFS-5232
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, hdfs-client, namenode
>    Affects Versions: Heterogeneous Storage (HDFS-2832)
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>         Attachments: HDFS-5232.01.patch
>
>
> Currently the StorageID is used to identify both the Datanode and the storage. This works
because we treat all storages attached to the Datanode as a single storage unit.
> We plan to replace the StorageID with two independent IDs:
> # Datanode UUID - this will be a string that uniquely identifies each Datanode in the
cluster. For upgraded clusters, the Datanode UUID will be the StorageID prior to the upgrade.
i.e. we will reuse the prior Storage ID.
> # Storage UUID - Each storage attached to the datanode will be identified by a UUID.

--
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

Mime
View raw message