Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Tue, 10 May 2011 06:08:03 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: 
 <1431676288.34007.1305007683129.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <104942528.33447.1304980983105.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HDFS-1906) Remove logging exception stack trace
 when one of the datanode targets to read from is not reachable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas resolved HDFS-1906.
-----------------------------------

    Resolution: Fixed

I committed the patch.

> 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