Re: Upgrade to Netty 4.x (1.19.2, 1.20.1 releases)

2025-01-20 Thread He Pin
n...@gmail.com 于2025年1月20日周一 18:38写道: > > > > > > > Hello, > > > > > > > > what about io.netty.maxDirectMemory [1]? Is it relevant? I haven't been > > > > able to understand exactly how much that changes, but I find it odd > > that, > > > >

Re: Upgrade to Netty 4.x (1.19.2, 1.20.1 releases)

2025-01-19 Thread He Pin
I think so, not sure how Flink works, but if they share the same key and running in the same JVM process, which can be. On 2025/01/18 16:58:15 Alexander Fedulov wrote: > @He Pin, > Thanks for bringing this up. > So, if I understand correctly, the problem is that there is currently no

Re: Upgrade to Netty 4.x (1.19.2, 1.20.1 releases)

2025-01-17 Thread He Pin
025 at 5:30 PM, Luke Chen wrote: > > > > > Thanks for the summary! > > > > > > +1 to upgrade Pekko to have netty 4 in 1.19.2 and 1.20.1 releases. > > > > > > Thanks. > > > Luke > > > > > > On Fri, Jan 17, 2025 at 7:50 PM He Pin wrot

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

2025-01-17 Thread He Pin
An update for this is going in https://lists.apache.org/thread/6lj5lbg18hz4n9zckn0b89p9mv9nz14g 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. > The memory leak is becau

Re: Upgrade to Netty 4.x (1.19.2, 1.20.1 releases)

2025-01-17 Thread He Pin
+1 to Netty 4 On 2025/01/16 15:12:40 Alexander Fedulov wrote: > Hi all, > > We have one remaining blocker for the 1.19.2 and 1.20.1 releases, namely > the issue associated with ticket FLINK-36510: *"Upgrade Pekko from 1.0.1 to > 1.1.2"* [1]. Here is the context: > >- The flink-rpc module is

Re: Future of classical remoting in Pekko

2023-09-25 Thread He Pin
m happy to help out, even making the Flink related changes when we're at > > > that point. > > > > > > [1] https://cwiki.apache.org/confluence/display/FLINK/1.18+Release > > > > > > --- Original Message --- > > > On Tuesday, Septemb

Re: Future of classical remoting in Pekko

2023-09-24 Thread He Pin
is the end of Sept [1], but I'm not > > > > > sure > > > > > everything will come together by then. Maybe it will pushed by a > > > > > couple > > > > > days. > > > > > > > > > > I'm happy to help

Re: Future of classical remoting in Pekko

2023-09-13 Thread He Pin
then. Maybe it will pushed by a couple days. > > I'm happy to help out, even making the Flink related changes when we're at > that point. > > [1] https://cwiki.apache.org/confluence/display/FLINK/1.18+Release > > --- Original Message --- > On Tuesday,

Re: Future of classical remoting in Pekko

2023-09-12 Thread He Pin
Hi Ferenc: What's the ETA of the Flink 1.18? I think we should beable to collaborate on this,and at work we are using Flink too. On 2023/09/12 15:16:11 Ferenc Csaky wrote: > Hi Matthew, > > Thanks for bringing this up! Cca half a year ago I started to work on an Akka > Artery migration, there i

Re: Future of classical remoting in Pekko

2023-09-12 Thread He Pin
The netty maintenance asked akka team to migrate once back in 2012, but they never have a chance to do that, and the multi node testkit has been upgraded to Netty 4 ,only the classic transport is based on Netty 3. In later version of Akka 2.8, they removed the classic transport too. I think we