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 89277101C6 for ; Mon, 22 Apr 2013 23:05:16 +0000 (UTC) Received: (qmail 65756 invoked by uid 500); 22 Apr 2013 23:05:16 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 65716 invoked by uid 500); 22 Apr 2013 23:05:16 -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 65704 invoked by uid 99); 22 Apr 2013 23:05:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 23:05:16 +0000 Date: Mon, 22 Apr 2013 23:05:16 +0000 (UTC) From: "Chris Nauroth (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-4725) fix HDFS file handle leaks 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-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-4725: -------------------------------- Status: Patch Available (was: Open) > fix HDFS file handle leaks > -------------------------- > > Key: HDFS-4725 > URL: https://issues.apache.org/jira/browse/HDFS-4725 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode, test, tools > Affects Versions: 3.0.0 > Reporter: Chris Nauroth > Assignee: Chris Nauroth > Attachments: HDFS-4725.1.patch > > > The scope of this issue is to fix multiple file handle leaks observed from recent HDFS test runs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira