Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 1 May 2012 22:24:56 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <900236776.15198.1335911096320.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HDFS-3342) SocketTimeoutException in
 BlockSender.sendChunks could have a better error message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Todd Lipcon created HDFS-3342:
---------------------------------

             Summary: SocketTimeoutException in BlockSender.sendChunks could have a better error message
                 Key: HDFS-3342
                 URL: https://issues.apache.org/jira/browse/HDFS-3342
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: data-node
    Affects Versions: 2.0.0
            Reporter: Todd Lipcon
            Priority: Minor


Currently, if a client connects to a DN and begins to read a block, but then stops calling read() for a long period of time, the DN will log a SocketTimeoutException "480000 millis timeout while waiting for channel to be ready for write." This is because there is no "keepalive" functionality of any kind. At a minimum, we should improve this error message to be an INFO level log which just says that the client likely stopped reading, so disconnecting it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira