You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Mukund Thakur (Jira)" <ji...@apache.org> on 2022/12/22 18:52:00 UTC
[jira] [Updated] (HADOOP-18105) Implement a variant of ElasticByteBufferPool which uses weak references for garbage collection.
[ https://issues.apache.org/jira/browse/HADOOP-18105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mukund Thakur updated HADOOP-18105:
-----------------------------------
Fix Version/s: 3.3.5
> Implement a variant of ElasticByteBufferPool which uses weak references for garbage collection.
> -----------------------------------------------------------------------------------------------
>
> Key: HADOOP-18105
> URL: https://issues.apache.org/jira/browse/HADOOP-18105
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: common, fs
> Reporter: Mukund Thakur
> Assignee: Mukund Thakur
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.5
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> Currently in hadoop codebase, we have two classes which implements byte buffers pooling.
> One is ElasticByteBufferPool which doesn't use weak references and thus could cause memory leaks in production environment.
> Other is DirectBufferPool which uses weak references but doesn't support caller's preference for either on-heap or off-heap buffers.
>
> The idea is to create an improved version of ElasticByteBufferPool by subclassing it ( as it is marked as public and stable and used widely in hdfs ) with essential functionalities required for effective buffer pooling. This is important for the parent Vectored IO work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org