[
https://issues.apache.org/jira/browse/HDFS-17907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18074114#comment-18074114
]
ASF GitHub Bot commented on HDFS-17907:
---------------------------------------
konstantinb opened a new pull request, #8438:
URL: https://github.com/apache/hadoop/pull/8438
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
HDFS-17907: Log DataXceiver client disconnect (Premature EOF) at INFO
instead of ERROR
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
### AI Tooling
If an AI tool was used:
- [ ] The PR includes the phrase "Contains content generated by <tool>"
where <tool> is the name of the AI tool used.
- [ ] My use of AI contributions follows the ASF legal policy
https://www.apache.org/legal/generative-tooling.html
> DataXceiver logs ERROR for "Premature EOF" on WRITE_BLOCK
> ---------------------------------------------------------
>
> Key: HDFS-17907
> URL: https://issues.apache.org/jira/browse/HDFS-17907
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Konstantin Bereznyakov
> Priority: Major
>
> DataXceiver logs ERROR for "Premature EOF" exceptions during WRITE_BLOCK
> operations. These are expected when clients disconnect during writes and
> should be logged at INFO/DEBUG level instead.
> [Affected
> Code|https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java#L309]
> *Current Behavior*
> ReplicaAlreadyExistsException during WRITE_BLOCK is already handled
> specially:
> if (op == Op.WRITE_BLOCK && t instanceof ReplicaAlreadyExistsException)
> { // logs at INFO/TRACE, not ERROR }
> But "Premature EOF" exceptions during WRITE_BLOCK fall through to ERROR
> logging, even though they are equally expected when clients abort writes.
> *Impact*
> - Unnecessary ERROR-level log noise in DataNode logs
> - Difficult to identify real errors among expected client disconnections
> - Inconsistent with existing ReplicaAlreadyExistsException handling
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
