[
https://issues.apache.org/jira/browse/HADOOP-19341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899060#comment-17899060
]
ASF GitHub Bot commented on HADOOP-19341:
-----------------------------------------
EungsopYoo opened a new pull request, #7168:
URL: https://github.com/apache/hadoop/pull/7168
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
The direct memory allocated by ElasticByteBufferPool of HDFS client is never
released.
We found that we already have the solution,
WeakReferencedElasticByteBufferPool.
Just replace ElasticByteBufferPool with WeakReferencedElasticByteBufferPool.
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> HDFS Client's direct memory leaks with erasure codind enabled
> -------------------------------------------------------------
>
> Key: HADOOP-19341
> URL: https://issues.apache.org/jira/browse/HADOOP-19341
> Project: Hadoop Common
> Issue Type: Bug
> Components: erasure-coding
> Reporter: Eungsop Yoo
> Priority: Major
> 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: [email protected]
For additional commands, e-mail: [email protected]
