[
https://issues.apache.org/jira/browse/HDFS-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818403#comment-17818403
]
ASF GitHub Bot commented on HDFS-17383:
---------------------------------------
ThinkerLei opened a new pull request, #6560:
URL: https://github.com/apache/hadoop/pull/6560
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
[HDFS-17383](https://issues.apache.org/jira/browse/HDFS-17383)
> 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
> Priority: Major
> 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: [email protected]
For additional commands, e-mail: [email protected]
