[
https://issues.apache.org/jira/browse/HDFS-17967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDFS-17967:
----------------------------------
Labels: pull-request-available (was: )
> Handle InvalidEncryptionKeyException in data-transfer connection setup paths
> -----------------------------------------------------------------------------
>
> Key: HDFS-17967
> URL: https://issues.apache.org/jira/browse/HDFS-17967
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 3.4.3
> Reporter: ZhenyuLi
> Priority: Major
> Labels: pull-request-available
>
> HDFS-17897 and HDFS-17899 added handling for
> InvalidEncryptionKeyException in several HDFS data-transfer connection
> paths.
> However, the following paths still do not retry when the cached data
> encryption
> key is rejected during the SASL handshake:
> * DataXceiver writeBlock mirror pipeline connection
> * DataXceiver replaceBlock proxy copy connection
> * Erasure coding StripedBlockWriter target connection
> In these paths, InvalidEncryptionKeyException is raised during the SASL
> data-transfer handshake, before the downstream writeBlock or copyBlock
> request
> is sent. Therefore, retrying the connection once is safe because no
> data-transfer operation has been issued yet.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
