[
https://issues.apache.org/jira/browse/FLINK-36510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908999#comment-17908999
]
He Pin commented on FLINK-36510:
--------------------------------
[~pj.fanning] [~fcsaky] I have double-checked the code on the Pekko side, the
current usage is right, and the `ByteBuf` is released correctly by the
`SimpleChannelInboundHandler`,
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 flink application needs this
`{{{}-Dio.netty.tryReflectionSetAccessible=true` to avoid OOM in production.{}}}
or , you could set the Netty's bytebuf allocator with `unpooled` by default.
> Upgrade Pekko from 1.0.1 to 1.1.2
> ---------------------------------
>
> Key: FLINK-36510
> URL: https://issues.apache.org/jira/browse/FLINK-36510
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Coordination
> Affects Versions: 1.20.0, 1.19.1, 2.0-preview
> Reporter: Grace Grimwood
> Assignee: Grace Grimwood
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.0, 1.19.2, 1.20.1
>
>
> Updates Pekko dependency to 1.1.2 which in turn upgrades Netty 3 to 4
> (addressing FLINK-29065 and removing several CVEs from Flink). Pekko 1.1 also
> upgrades other dependencies such as slf4j and Jackson. For more details see
> the [Pekko 1.1 release
> notes|https://pekko.apache.org/docs/pekko/current/release-notes/releases-1.1.html].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
