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 "Pieter Reuse (JIRA)" <ji...@apache.org> on 2016/10/20 13:01:58 UTC

[jira] [Commented] (HDFS-6708) StorageType should be encoded in the block token

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

Pieter Reuse commented on HDFS-6708:
------------------------------------

The changes in the protobuf for the BlockTokenIdentifier will be discussed and potentially implemented in [HDFS-11026|https://issues.apache.org/jira/browse/HDFS-11026]. I've made great progress in implementing a patch for this ticket, but will rebase implementation on top of the patch for HDFS-11026 before uploading it here (avoiding double review-work).

> StorageType should be encoded in the block token
> ------------------------------------------------
>
>                 Key: HDFS-6708
>                 URL: https://issues.apache.org/jira/browse/HDFS-6708
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>    Affects Versions: 2.4.1
>            Reporter: Arpit Agarwal
>            Assignee: Pieter Reuse
>
> HDFS-6702 is adding support for file creation based on StorageType.
> The block token is used as a tamper-proof channel for communicating block parameters from the NN to the DN during block creation. The StorageType should be included in this block token.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org