You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Ayush Saxena (Jira)" <ji...@apache.org> on 2023/04/29 11:57:00 UTC
[jira] [Commented] (HDFS-16897) Fix abundant Broken pipe exception in BlockSender
[ https://issues.apache.org/jira/browse/HDFS-16897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717903#comment-17717903 ]
Ayush Saxena commented on HDFS-16897:
-------------------------------------
Committed to trunk.
Thanx [~fanluoo] for the contribution!!!
Note: Added [~fanluoo] as HDFS contributor to assign the ticket
> Fix abundant Broken pipe exception in BlockSender
> -------------------------------------------------
>
> Key: HDFS-16897
> URL: https://issues.apache.org/jira/browse/HDFS-16897
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 3.3.4
> Reporter: fanluo
> Assignee: fanluo
> Priority: Minor
> Labels: pull-request-available
>
> in our production cluster env , we found some exception in datanode logs，its frequently print below error
> in HDFS-2054 we only ignored message starting with `Broken pipe` which may not enough for the following case:
> !https://user-images.githubusercontent.com/20748856/215264829-5f16dbc3-fea2-4883-a3d6-ded367564b8c.png!
> this situation look like related to short-circuit read. in HDFS-4354 the error has been wrapped, so that our previous judgment conditions are invalid.
> !https://user-images.githubusercontent.com/20748856/215314257-2064637b-ea46-42f5-b53f-a29e68bb50ea.png!
> maybe we can improve it.
--
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