You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2013/09/22 01:48:53 UTC
[jira] [Commented] (HDFS-5233) Use Datanode UUID to identify
Datanodes
[ https://issues.apache.org/jira/browse/HDFS-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773927#comment-13773927 ]
Tsz Wo (Nicholas), SZE commented on HDFS-5233:
----------------------------------------------
There are some spaces incorrectly added.
{code}
- * transfer, and that may be a different address.
+ * transfer, and that may be a different address.
{code}
+1 on the patch once it is reverted.
> Use Datanode UUID to identify Datanodes
> ---------------------------------------
>
> Key: HDFS-5233
> URL: https://issues.apache.org/jira/browse/HDFS-5233
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, namenode
> Affects Versions: Heterogeneous Storage (HDFS-2832)
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Attachments: HDFS-5233.01.patch, HDFS-5233.02.patch
>
>
> StorageID currently identifies both a Datanode and a storage attached to the Datanode. Once we start tracking multiple storages per datanode we would like to deprecate StorageID in favor of a DatanodeUuid for the datanode and a StorageUuid per storage.
> This Jira track replacing StorageID with DatanodeUuid wherever it is used to identify a Datanode.
--
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