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 "Chris Nauroth (Jira)" <ji...@apache.org> on 2026/03/22 16:54:00 UTC

[jira] [Resolved] (HDFS-4277) SocketTimeoutExceptions over the DataXciever service of a DN should print the DFSClient ID

     [ https://issues.apache.org/jira/browse/HDFS-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth resolved HDFS-4277.
---------------------------------
    Fix Version/s: 3.5.0
                   3.4.4
     Hadoop Flags: Reviewed
         Assignee: Amit Balode
       Resolution: Fixed

> SocketTimeoutExceptions over the DataXciever service of a DN should print the DFSClient ID
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4277
>                 URL: https://issues.apache.org/jira/browse/HDFS-4277
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 2.0.0-alpha
>            Reporter: Harsh J
>            Assignee: Amit Balode
>            Priority: Minor
>              Labels: newbie, pull-request-available
>             Fix For: 3.5.0, 3.4.4
>
>
> Currently, when one faces a SocketTimeoutExceptions (or any exception rather, in a DN log, for a client <-> DN interaction), we fail to print the DFSClient ID. This makes it untraceable (like is it a speculative MR caused timeout, or a RS crash, etc.).



--
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