He-Pin commented on PR #25866:
URL: https://github.com/apache/flink/pull/25866#issuecomment-2566221237
So I suggest:
rerun the tests with -Dio.netty.tryReflectionSetAccessible=true and
-Dio.netty.leakDetection.level=PARANOID to see why and where it leaks or gets a
heap dump.
We have some applications, not a flink application still needs this
`-Dio.netty.tryReflectionSetAccessible=true` to avoid OOM in production.
or , you could set the Netty's bytebuf allocator with `unpooled` by default.
with `-Dio.netty.allocator.type=unpooled`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
