-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HADOOP-19341] HDFS Client's direct memory leaks with erasure coding enabled #7168
base: trunk
Are you sure you want to change the base?
Conversation
💔 -1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How have you tested the patch ?
...p-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/ElasticByteBufferPool.java
Show resolved
Hide resolved
b218980
to
9d5bc0a
Compare
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
I think the filed tests are not related to this PR, retrigger the checks. |
💔 -1 overall
This message was automatically generated. |
|
||
import java.nio.ByteBuffer; | ||
|
||
public class TestElasticByteBufferPool { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are just testing the WeakReferencedElasticByteBufferPool here as well with just using the abstract base class. I think this is just duplicate and you can just change all the instances of base class in the TestWeakReferencedElasticByteBufferPool
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💔 -1 overall
This message was automatically generated. |
Not sure why yetus is giving the license error now. can you retrigger it and we are good to go. |
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:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?