hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1568) Improve DataXceiver error logging
Date Thu, 19 May 2011 20:30:47 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036434#comment-13036434
] 

Tsz Wo (Nicholas), SZE commented on HDFS-1568:
----------------------------------------------

- Could you not reformat the message in this?  Otherwise, it is hard to review the patch.
 You may fix the message format in a separated JIRA.
{code}
-          block + " to " +
-                s.getInetAddress() + ":\n" + 
-                StringUtils.stringifyException(ioe) );
+               block + " to " +
+               remoteAddress + ":\n" + 
+               StringUtils.stringifyException(ioe) );
{code}

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

Mime
View raw message