[
https://issues.apache.org/jira/browse/HDFS-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626596#comment-14626596
]
Walter Su commented on HDFS-8433:
---------------------------------
I have another idea: Pick up the {{BlockIdRange}} idea again in 01 patch. This
time, we don't need {{BlockIdRange}} class. We extends the fields of
{{BlockTokenIdentifier}}. (See BlockTokenIdentifier#readFields(..) / write(..) )
Just add a field {{IdRange}}, default value is 0.
I think the performance impact on contiguous block is little. And I think it
also support old DN, old DN just doesn't read the last field.
I prefer to implement this against trunk. And just merge 02 patch(multiple
tokens method) into feature branch and see how it works. Then we decide if it's
worth to pick up BlockIdRange.
Hi, [~jingzhao], [~szetszwo]! Any idea?
> 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
>
>
> 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)
