[
https://issues.apache.org/jira/browse/HDFS-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lei w updated HDFS-17383:
-------------------------
Description: We found that transfer block failed during the namenode
upgrade. The specific error reported was that the block token verification
failed. The reason is that during the datanode transfer block process, the
source datanode uses its own generated block token, and the keyid comes from
ANN or SBN. However, because the newly upgraded NN has just been started, the
keyid owned by the source datanode may not be owned by the target datanode, so
the write fails. Here's how to reproduce this situation.
> Use the block token from active NameNode to transfer block in DataNode
> ----------------------------------------------------------------------
>
> Key: HDFS-17383
> URL: https://issues.apache.org/jira/browse/HDFS-17383
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: lei w
> Priority: Major
>
> We found that transfer block failed during the namenode upgrade. The specific
> error reported was that the block token verification failed. The reason is
> that during the datanode transfer block process, the source datanode uses its
> own generated block token, and the keyid comes from ANN or SBN. However,
> because the newly upgraded NN has just been started, the keyid owned by the
> source datanode may not be owned by the target datanode, so the write fails.
> Here's how to reproduce this situation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
