Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <2098058093.1227558584304.JavaMail.jira@brutus>
Date: Mon, 24 Nov 2008 12:29:44 -0800 (PST)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4655) FileSystem.CACHE should be
 ref-counted
In-Reply-To: <1633844090.1226608604134.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650310#action_12650310 ] 

dhruba borthakur commented on HADOOP-4655:
------------------------------------------

>'Yes, closing a FileSystem that's in use by other threads can break things. But what harm is this causing in practice?

My patke is that this patch makes it easier for an application program to use the FileSystem object. RefCounting the objects make it easier for users of this API to use FileSystem object: they need not know about the existence of the cache. Maybe we can label it as a "improvement"  rather than a "bug".

> FileSystem.CACHE should be ref-counted
> --------------------------------------
>
>                 Key: HADOOP-4655
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4655
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs, fs
>    Affects Versions: 0.18.1, 0.18.2, 0.19.0, 0.19.1, 0.20.0
>            Reporter: Hong Tang
>
> FileSystem.CACHE is not ref-counted, and could lead to resource leakage.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.