JHSUYU opened a new pull request, #8364:
URL: https://github.com/apache/hadoop/pull/8364
### Description of PR
Jira: [HDFS-17897](https://issues.apache.org/jira/browse/HDFS-17897)
HDFS-12931 added handling for `InvalidEncryptionKeyException` in
`ReplicatedFileChecksumComputer.checksumBlock()` but missed the parallel
striped file path `StripedFileNonStripedChecksumComputer.checksumBlockGroup()`.
Both paths call `DFSClient.connectToDN()`, which performs a SASL handshake
using a cached `DataEncryptionKey` (DEK). When the DEK references a `BlockKey`
that has been removed from the DataNode (there is
a time gap when the DataNode isn't updated with the new keys after key
rotation, as described in
[HDFS-12931](https://issues.apache.org/jira/browse/HDFS-12931)), the handshake
fails with `InvalidEncryptionKeyException`.
In the replicated path, this exception is caught,
`clearDataEncryptionKey()` is called to invalidate the cached DEK, and the
block is retried. In the striped path, the exception falls through to the
generic `catch (IOException)` block, which only logs a warning. The stale
DEK is never cleared, so every DataNode in the block group fails with the same
error. The operation fails permanently — even
user-level retries will reuse the same stale cached DEK.
**Fix:** Add `catch (InvalidEncryptionKeyException)` in
`checksumBlockGroup()`, mirroring the existing handling in `checksumBlock()`.
### How was this patch tested?
- Added `testStripedFileChecksumWithInvalidEncryptionKey` in
`TestEncryptedTransfer`, which creates an EC file, invalidates the encryption
key on all DataNodes, and verifies that `getFileChecksum()` succeeds by
catching the exception and refreshing the key.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
