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 Fri, 10 Jul 2015 00:16:04 GMT

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

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

The issue with the changes on BlockTokenIdentifier's serialization/deserialization is that
it can break the compatibility between a new NN and old DataNodes. Then during the rolling
upgrade process, after we upgrade the NN, the block token retrieved from the new NN cannot
be parsed by old DataNodes anymore, even if the token is actually for a non-striped block.

Therefore instead of the current solution, can we let NN return multiple block tokens for
a striped block group?

> 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.00.patch, HDFS-8433.01.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