[
https://issues.apache.org/jira/browse/HDFS-17670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran moved HADOOP-19341 to HDFS-17670:
------------------------------------------------
Component/s: erasure-coding
(was: erasure-coding)
Key: HDFS-17670 (was: HADOOP-19341)
Project: Hadoop HDFS (was: Hadoop Common)
> HDFS Client's direct memory leaks with erasure coding enabled
> -------------------------------------------------------------
>
> Key: HDFS-17670
> URL: https://issues.apache.org/jira/browse/HDFS-17670
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: erasure-coding
> Reporter: Eungsop Yoo
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2024-11-18-13-53-23-690.png
>
>
> We are testing erasure coding with HBase. But we faced that the size of
> direct memory of HBase RegionServer keep growing.
> !image-2024-11-18-13-53-23-690.png!
> It is caused by that the direct memory allocated by ElasticByteBufferPool of
> HDFS client is never released.
> https://issues.apache.org/jira/browse/HADOOP-18105
> We found that we already have the solution,
> WeakReferencedElasticByteBufferPool.
> Just replace ElasticByteBufferPool with WeakReferencedElasticByteBufferPool.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
