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 "Harsh J (JIRA)" <ji...@apache.org> on 2012/12/05 20:57:58 UTC

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

Harsh J created HDFS-4277:
-----------------------------

             Summary: 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: Bug
          Components: datanode
    Affects Versions: 2.0.0-alpha
            Reporter: Harsh J
            Priority: Minor


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Posted by "Harsh J (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HDFS-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harsh J updated HDFS-4277:
--------------------------

    Issue Type: Improvement  (was: Bug)
    
> 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
>            Priority: Minor
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira