[
https://issues.apache.org/jira/browse/HDFS-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shuyan Zhang resolved HDFS-17383.
---------------------------------
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Target Version/s: 3.5.0
Assignee: lei w
Resolution: Fixed
> Datanode current block token should come from active NameNode in HA mode
> ------------------------------------------------------------------------
>
> Key: HDFS-17383
> URL: https://issues.apache.org/jira/browse/HDFS-17383
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: lei w
> Assignee: lei w
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
> Attachments: reproduce.diff
>
>
> 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 in the attachment
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
