Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ABFD51721E for ; Sun, 5 Oct 2014 18:01:34 +0000 (UTC) Received: (qmail 15366 invoked by uid 500); 5 Oct 2014 18:01:34 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 15319 invoked by uid 500); 5 Oct 2014 18:01:34 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 15131 invoked by uid 99); 5 Oct 2014 18:01:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Oct 2014 18:01:34 +0000 Date: Sun, 5 Oct 2014 18:01:34 +0000 (UTC) From: "Yongjun Zhang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated HDFS-3342: -------------------------------- Status: Patch Available (was: Open) > 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: datanode > Affects Versions: 2.0.0-alpha > Reporter: Todd Lipcon > Assignee: Yongjun Zhang > Priority: Minor > Attachments: HDFS-3342.001.patch > > > 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 was sent by Atlassian JIRA (v6.3.4#6332)