[
https://issues.apache.org/jira/browse/HDFS-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837042#comment-17837042
]
ASF GitHub Bot commented on HDFS-17383:
---------------------------------------
ThinkerLei commented on PR #6562:
URL: https://github.com/apache/hadoop/pull/6562#issuecomment-2054527922
@zhangshuyan0 Thank you very much for your comment. The case you mentioned
has been fixed. When there is no active namenode, the currentKey will be set to
one of the standby nodes. When a failover occurs, the active namenode will
proactively trigger the distribution of the key to the DataNode to promptly
modify the currentKey.
> 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
> Labels: pull-request-available
> 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]
