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-1906) Remove logging exception stack trace when one of the datanode targets to read from is not reachable
Date Mon, 09 May 2011 23:10:03 GMT

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

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

+1 patch looks good.

> Remove logging exception stack trace when one of the datanode targets to read from is
not reachable
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1906
>                 URL: https://issues.apache.org/jira/browse/HDFS-1906
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs client
>    Affects Versions: 0.20.203.1
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Minor
>             Fix For: 0.23.0
>
>         Attachments: HDFS-1906.2.patch, HDFS-1906.patch
>
>
> When client fails to connect to one of the datanodes from the list of block locations
returned, exception stack trace is printed in the client log. This is an expected failure
scenario that is handled at the client, by going to the next location. Printing entire stack
trace is unnecessary and just printing the exception message should be sufficient.

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

Mime
View raw message