Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 64947 invoked from network); 14 May 2008 23:02:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 May 2008 23:02:17 -0000 Received: (qmail 10261 invoked by uid 500); 14 May 2008 23:02:18 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 10218 invoked by uid 500); 14 May 2008 23:02:18 -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 10203 invoked by uid 99); 14 May 2008 23:02:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 May 2008 16:02:18 -0700 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; Wed, 14 May 2008 23:01:40 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 97CCB234C112 for ; Wed, 14 May 2008 16:01:55 -0700 (PDT) Message-ID: <232197874.1210806115620.JavaMail.jira@brutus> Date: Wed, 14 May 2008 16:01:55 -0700 (PDT) From: "Raghu Angadi (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3382) Memory leak when files are not cleanly closed In-Reply-To: <416013419.1210704115712.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-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596974#action_12596974 ] Raghu Angadi commented on HADOOP-3382: -------------------------------------- TestMiniMRBingUp failes. This is very simple test and does not even use DFS. The failure seems to another case of HADOOP-3354 (thanks Lohit). I think this patch can be committed. > Memory leak when files are not cleanly closed > --------------------------------------------- > > Key: HADOOP-3382 > URL: https://issues.apache.org/jira/browse/HADOOP-3382 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.16.0 > Reporter: Raghu Angadi > Assignee: Raghu Angadi > Priority: Blocker > Fix For: 0.17.0 > > Attachments: HADOOP-3382.patch, HADOOP-3382.patch, HADOOP-3382.patch, memleak.txt > > > {{FSNamesystem.internalReleaseCreate()}} in invoked on files that are open for writing but not cleanly closed. e.g. when client invokes {{abandonFileInProgress()}} or when lease expires. It deletes the last block if it has a length of zero. The block is deleted from the file INode but not from {{blocksMap}}. Then leaves a reference to such file until NameNode is restarted. When this happens HADOOP-3381 multiplies amount of memory leak. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.