hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6708) StorageType should be encoded in the block token
Date Wed, 22 Mar 2017 20:34:42 GMT

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

Chris Douglas commented on HDFS-6708:
-------------------------------------

+1 This looks good to me, too.

[~daryn] do you have an opinion on backwards compatibility for the Writable case? I suspect
older clients will ignore the extra fields harmlessly- these should be framed in the RPC-
but I haven't actually verified.

> 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: Ewan Higgs
>             Fix For: 3.0.0-alpha3
>
>         Attachments: HDFS-6708.0001.patch, HDFS-6708.0002.patch, HDFS-6708.0003.patch,
HDFS-6708.0004.patch, HDFS-6708.0005.patch, HDFS-6708.0006.patch
>
>
> 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.15#6346)

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


Mime
View raw message