hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8433) blockToken is not set in constructInternalBlock and parseStripedBlockGroup in StripedBlockUtil
Date Wed, 15 Jul 2015 17:58:05 GMT

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

Jing Zhao commented on HDFS-8433:
---------------------------------

In 03 patch, when checking the block token, the {{BlockTokenSecrectManager}} still uses a
{{BlockTokenIdentifier}} to parse the ID of the token, thus if both sides are new DataNodes,
the ID range information cannot be retrieved. 

> blockToken is not set in constructInternalBlock and parseStripedBlockGroup in StripedBlockUtil
> ----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-8433
>                 URL: https://issues.apache.org/jira/browse/HDFS-8433
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Walter Su
>         Attachments: HDFS-8433-HDFS-7285.02.patch, HDFS-8433.00.patch, HDFS-8433.01.patch,
HDFS-8433.03.PoC.patch
>
>
> The blockToken provided in LocatedStripedBlock is not used to create LocatedBlock in
constructInternalBlock and parseStripedBlockGroup in StripedBlockUtil.
> We should also add ec tests with security on.



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

Mime
View raw message