[
https://issues.apache.org/jira/browse/HDFS-11956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059663#comment-16059663
]
Ewan Higgs commented on HDFS-11956:
-----------------------------------
Hi,
Another idea is to just ignore the BlockTokenIdentifier if the storageId list
in the request is empty. The current intention of the storageId in the message
is just a suggestion for the datanode in most cases; but in the case of
provided storage (HDFS-9806) it will be the storageId of the provided storage
system. If the storageId list is empty then it will just fail the write to the
provided storage since it won't know where/how to write it.
> Fix BlockToken compatibility with Hadoop 2.x clients
> ----------------------------------------------------
>
> Key: HDFS-11956
> URL: https://issues.apache.org/jira/browse/HDFS-11956
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha4
> Reporter: Andrew Wang
> Assignee: Ewan Higgs
> Priority: Blocker
> Attachments: HDFS-11956.001.patch, HDFS-11956.002.patch,
> HDFS-11956.003.patch
>
>
> Seems like HDFS-9807 broke backwards compatibility with Hadoop 2.x clients.
> When talking to a 3.0.0-alpha4 DN with security on:
> {noformat}
> 2017-06-06 23:27:22,568 WARN org.apache.hadoop.hdfs.server.datanode.DataNode:
> Block token verification failed: op=WRITE_BLOCK,
> remoteAddress=/172.28.208.200:53900, message=Block token with StorageIDs
> [DS-c0f24154-a39b-4941-93cd-5b8323067ba2] not valid for access with
> StorageIDs []
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
