Re: Memory leak in pekko's Netty 4 transport.

It is recommended that you revert back to Pekko 1.0 which uses Netty 3. We will notify you when Pekko 1.1.3 is released. On 2024/12/28 14:54:02 kerr wrote: > First, super sorry about this. > https://github.com/apache/pekko/pull/1635 > > I just noticed this issue and did a quick check about it. >

Re: Memory leak in pekko's Netty 4 transport.

We don't have any changes in 1.1.3 that might help Flink. We haven't yet tracked down a reproducible case that doesn't involve running the Flink tests. See https://github.com/apache/pekko/issues/1634 On Mon, 6 Jan 2025 at 16:17, Alexander Fedulov wrote: > > @PJ Fanning,

[jira] [Created] (FLINK-33505) switch away from using netty 3 based Pekko Classic Remoting

PJ Fanning created FLINK-33505: -- Summary: switch away from using netty 3 based Pekko Classic Remoting Key: FLINK-33505 URL: https://issues.apache.org/jira/browse/FLINK-33505 Project: Flink

[jira] [Created] (FLINK-34541) Flink uses insecure http confluent endpoint in its build

PJ Fanning created FLINK-34541: -- Summary: Flink uses insecure http confluent endpoint in its build Key: FLINK-34541 URL: https://issues.apache.org/jira/browse/FLINK-34541 Project: Flink Issue