[
https://issues.apache.org/jira/browse/HDFS-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054176#comment-13054176
]
Bharath Mundlapudi commented on HDFS-2092:
------------------------------------------
Hi Eli,
>> Does this change mean that a Configuration object can now bee free'd because
>> there's one fewer ref to it?
Yes, the direction of this patch is that. Eventually, we will be passing around
only the DFSClient#conf or only required parameters to the downstream. This
will be a big change and needs border discussion. But you are right, the idea
is to stop having references to the conf object coming from the users. We want
to let client code to decide the scope of conf object.
Regarding memory, these will be few [key,value] pairs copied into DFSClient but
then will be freeing the blotted conf object for the GC. That will be a big win
on memory.
> 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
