ZhenyuLi created HDFS-17899:
-------------------------------
Summary: 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
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
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.
Testing: Four unit tests added, all confirmed to fail when the fix is
reverted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
