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 "Joey Echeverria (JIRA)" <ji...@apache.org> on 2011/06/18 15:31:47 UTC

[jira] [Updated] (HDFS-1568) Improve DataXceiver error logging

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

Joey Echeverria updated HDFS-1568:
----------------------------------

    Status: Open  (was: Patch Available)

Canceling patch to upload one rebased to trunk.

> Improve DataXceiver error logging
> ---------------------------------
>
>                 Key: HDFS-1568
>                 URL: https://issues.apache.org/jira/browse/HDFS-1568
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Joey Echeverria
>            Priority: Minor
>              Labels: newbie
>         Attachments: HDFS-1568-1.patch, HDFS-1568-3.patch, HDFS-1568-4.patch, HDFS-1568-5.patch, HDFS-1568-output-changes.patch
>
>
> In supporting customers we often see things like SocketTimeoutExceptions or EOFExceptions coming from DataXceiver, but the logging isn't very good. For example, if we get an IOE while setting up a connection to the downstream mirror in writeBlock, the IP of the downstream mirror isn't logged on the DN side.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira