Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 14 Jul 2011 17:45:00 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <954853453.14233.1310665500246.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1354292315.7783.1307642520043.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2054) BlockSender.sendChunk() prints ERROR
 for connection closures encountered  during transferToFully()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas commented on HDFS-2054:
---------------------------------------

I missed Jakob's comment as I had not looked though all the comments. I looked at HDFS-2054-2.patch, I still see it. The committed code does not have it though. 

Just wanted to make sure we are all aware of need to remove StringifyException.

> BlockSender.sendChunk() prints ERROR for connection closures encountered  during transferToFully()
> --------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-2054
>                 URL: https://issues.apache.org/jira/browse/HDFS-2054
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node
>    Affects Versions: 0.22.0, 0.23.0
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>            Priority: Minor
>             Fix For: 0.22.0, 0.23.0
>
>         Attachments: HDFS-2054-1.patch, HDFS-2054-2.patch, HDFS-2054.patch, HDFS-2054.patch, HDFS-2054.patch
>
>
> The addition of ERROR was part of HDFS-1527. In environments where clients tear down FSInputStream/connection before reaching the end of stream, this error message often pops up. Since these are not really errors and especially not the fault of data node, the message should be toned down at least. 

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