Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 23 Jun 2011 22:56:47 +0000 (UTC)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <2105883186.34893.1308869807547.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1271780704.23333.1308632387413.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2092) Remove configuration object
 reference in DFSClient
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054159#comment-13054159 ] 

Eli Collins commented on HDFS-2092:
-----------------------------------

Does this change mean that a Configuration object can now bee free'd because there's one fewer ref to it?  Otherwise it seems like we're now allocating a DFSClient#conf in addition to a Configuration object which increases over all memory usage no?

> Remove configuration object reference in DFSClient
> --------------------------------------------------
>
>                 Key: HDFS-2092
>                 URL: https://issues.apache.org/jira/browse/HDFS-2092
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.23.0
>            Reporter: Bharath Mundlapudi
>            Assignee: Bharath Mundlapudi
>             Fix For: 0.23.0
>
>         Attachments: HDFS-2092-1.patch, HDFS-2092-2.patch
>
>
> At present, DFSClient stores reference to configuration object. Since, these configuration objects are pretty big at times can blot the processes which has multiple DFSClient objects like in TaskTracker. This is an attempt to remove the reference of conf object in DFSClient. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira