[
https://issues.apache.org/jira/browse/RATIS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898817#comment-17898817
]
Ivan Andika commented on RATIS-2189:
------------------------------------
{quote}[~ivanandika] , your version may not have HDDS-9081 and RATIS-1868.
They are causing "OutOfMemoryError: Direct buffer memory".
Actually, your versions are quite new. They should already have HDDS-9081 and
RATIS-1868.
{quote}
[~szetszwo] Thanks for the suggestion. Yes, the Ozone and Ratis under tests
already contain these patches.
We are currently trying to identify and resolve some ByteBuf memory leaks that
might contribute to the OOM issue.
> Use ByteBufAllocator#ioBuffer in NettyDataStreamUtils
> -----------------------------------------------------
>
> Key: RATIS-2189
> URL: https://issues.apache.org/jira/browse/RATIS-2189
> Project: Ratis
> Issue Type: Improvement
> Components: Streaming
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Minor
> Fix For: 3.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, NettyDataStreamUtils uses ByteBufAllocator#directBuffer which
> forces all ByteBufAllocator to allocate direct buffer even for
> PreferHeapByteBufAllocator (e.g. when we set
> -Dorg.apache.ratis.thirdparty.io.netty.noPreferDirect=true).
> It's better to use ioBuffer and delegates to the actual ByteBufAllocator to
> the type of memory it will use.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
