Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 86952 invoked from network); 17 Jan 2009 00:14:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Jan 2009 00:14:25 -0000 Received: (qmail 28221 invoked by uid 500); 17 Jan 2009 00:14:22 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 28187 invoked by uid 500); 17 Jan 2009 00:14:22 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 28176 invoked by uid 99); 17 Jan 2009 00:14:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jan 2009 16:14:22 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Jan 2009 00:14:20 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A1C93234C48C for ; Fri, 16 Jan 2009 16:13:59 -0800 (PST) Message-ID: <1264095677.1232151239661.JavaMail.jira@brutus> Date: Fri, 16 Jan 2009 16:13:59 -0800 (PST) From: "Raghu Angadi (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-4862) A spuriou IOException log on DataNode is not completely removed In-Reply-To: <1835604500.1229121044192.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghu Angadi updated HADOOP-4862: --------------------------------- Description: HADOOP-3678 fixes a spurious warning log in DataNode, in most cases. This log is still possible in some cases. For e.g. The exception is still logged if the client closes the connection after DataNode writes all the block data but before it writes final 4 bytes to indicate end of data. was: HADOOP-3678 fixes a spurious warning log in DataNode, in most cases. This log is still possible in some cases. For e.g. The exception is still logged if the client closes the connection after DataNode writes all the block data but before it writes final 4 bytes to indicate end of data. Priority: Blocker (was: Major) > A spuriou IOException log on DataNode is not completely removed > --------------------------------------------------------------- > > Key: HADOOP-4862 > URL: https://issues.apache.org/jira/browse/HADOOP-4862 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.18.2 > Reporter: Raghu Angadi > Assignee: Raghu Angadi > Priority: Blocker > Fix For: 0.19.1 > > Attachments: HADOOP-4862-branch-18.patch, HADOOP-4862.patch > > > HADOOP-3678 fixes a spurious warning log in DataNode, in most cases. This log is still possible in some cases. > For e.g. The exception is still logged if the client closes the connection after DataNode writes all the block data but before it writes final 4 bytes to indicate end of data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.