balodesecurity opened a new pull request, #8271: URL: https://github.com/apache/hadoop/pull/8271
## Summary - When a `SocketTimeoutException` (or other error) occurs in the DataXceiver service, the log messages did not include the DFSClient ID, making it impossible to trace which client caused the error. - Added `previousOpClientName` (the DFSClient ID) to the shared error string in `run()`'s catch block, which covers all error paths including `SocketTimeoutException` during `READ_BLOCK`. - Also added `clientName` to exception log messages directly in `readBlock()`, `writeBlock()`, and `transferBlock()` for completeness. ## Changes - `DataXceiver.run()`: include `previousOpClientName` in the error string used across all exception branches - `DataXceiver.readBlock()`: add `clientName` to `SocketException` (TRACE) and `IOException` (WARN) log messages - `DataXceiver.writeBlock()`: add `clientname` to the `IOException` log message - `DataXceiver.transferBlock()`: add `clientName` to the `IOException` log message ## Test plan - [ ] Existing `TestDataXceiverBackwardsCompat` passes - [ ] Existing `TestDataXceiverLazyPersistHint` passes - [ ] CI (Yetus) build passes on trunk 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
