[ 
https://issues.apache.org/jira/browse/HDFS-17967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wei-Chiu Chuang resolved HDFS-17967.
------------------------------------
    Fix Version/s: 3.6.0
       Resolution: Fixed

>  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
>             Fix For: 3.6.0
>
>
>  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
> With data-transfer encryption enabled, block-key rotation or transient RPC 
> failures delaying key propagation can leave DataNodes temporarily out of 
> sync. The SASL handshake then fails with InvalidEncryptionKeyException.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to