[jira] [Commented] (HDFS-17899) Handle InvalidEncryptionKeyException in Balancer Dispatcher, SPS BlockDispatcher and DataNode DataTransfer

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-17899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070857#comment-18070857 ] 

ASF GitHub Bot commented on HDFS-17899:
---------------------------------------

JHSUYU commented on PR #8383:
URL: https://github.com/apache/hadoop/pull/8383#issuecomment-4183922360

   Hi @jojochuang , sorry to nudge again. Any feedback would be greatly appreciated — happy to revise based on your suggestions!




> Handle InvalidEncryptionKeyException in Balancer Dispatcher, SPS  BlockDispatcher and DataNode DataTransfer
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-17899
>                 URL: https://issues.apache.org/jira/browse/HDFS-17899
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer & mover, datanode, encryption
>    Affects Versions: 3.4.1
>            Reporter: ZhenyuLi
>            Assignee: ZhenyuLi
>            Priority: Major
>              Labels: pull-request-available
>
>   This is a follow-up of HDFS-17897.
>   HDFS-17897 fixed {{InvalidEncryptionKeyException}} handling in DFSClient read/write and striped file checksum paths. However, three other
>   code paths that establish SASL-encrypted connections still lack this handling:
>   {{Dispatcher.PendingMove.dispatch()}} — Balancer block moves
>   {{BlockDispatcher.moveBlock()}} — SPS block moves
>   {{DataNode.DataTransfer.run()}} — DataNode block replication
>   When {{dfs.encrypt.data.transfer=true}} and block keys rotate, these paths are possible to fail with {{InvalidEncryptionKeyException}} and the stale key stays cached, causing all subsequent transfers to fail until process restart.
>   Fix: Add the same retry pattern to all three paths — catch the exception,
>   clear the cached encryption key via a new {{clearDataEncryptionKey()}} default
>    method on {{DataEncryptionKeyFactory}}, and retry once with a fresh key.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org