-
Notifications
You must be signed in to change notification settings - Fork 141
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
[Bug] Direct memory may leak in shuffle server. #1152
Comments
We add these startup options to analyse:
Then we found these logs
We found NettyManagedBuffer in incubator-uniffle/server/src/main/java/org/apache/uniffle/server/buffer/ShuffleBuffer.java Line 170 in 5ac76e8
I search the code. ManagedBuffer::release is only called in NETTY mode. |
3 tasks
Great work! |
zhengchenyu
added a commit
to zhengchenyu/incubator-uniffle
that referenced
this issue
Aug 17, 2023
jerqi
pushed a commit
that referenced
this issue
Aug 17, 2023
### What changes were proposed in this pull request? Release buffer when since the buffer have copied to data of reply. ### Why are the changes needed? Fix: #1152 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Test in cluster manually.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code of Conduct
Search before asking
Describe the bug
Direct memory may leak in shuffle server.
In client side, some task failed, Found error log:
due to io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: deadline exceeded after 59.999950602s.
And then I found shuffle server have many oom log:
Monitor shows that the direct memory of shuffle server have reached 80G (MaxDirectMemorySize is just 80G).
Affects Version(s)
master
Uniffle Server Log Output
No response
Uniffle Engine Log Output
No response
Uniffle Server Configurations
some key configuration:
Uniffle Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: