It's come to my attention that Flink is using Pekko's classical remoting,
if this is the case then I would recommend making a response at
https://lists.apache.org/thread/19h2wrs2om91g5vhnftv583fo0ddfshm .
Quick summary of what is being discussed is what to do with Pekko's
classical remoting. Class
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
Hi Matthew,
Thanks for bringing this up! Cca half a year ago I started to work on an Akka
Artery migration, there is a draft PR for that [1]. It might be an option to
revive that work and point it against Pekko instead. Although I would highlight
FLINK-29281 [2] which will replace the whole RPC
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
The target release date for 1.18 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 out, even making the Flink related changes when we're at that
point.
[1] https://cwiki.apache.org/confluence/display/FLINK/1.
Thanks, The PR[1] is ready now, would you like to help review it, thanks.
1. https://github.com/apache/incubator-pekko/pull/643
On 2023/09/13 09:20:48 Ferenc Csaky wrote:
> The target release date for 1.18 is the end of Sept [1], but I'm not sure
> everything will come together by then. Maybe it
I think that the end of September is too soon for a Pekko 1.1.x, there are
still more things
that we would like to merge before making a release.
Good news is that the PR to migrate to netty4 for classic remoting has been
merged
(see https://github.com/apache/incubator-pekko/pull/643). Improvement
I think that is totally fine, because any Pekko related changes can only be
added to the first patch release of 1.18 at this point, as there is an RC0 [1]
already so the release process will be initiated soon.
I am glad the mentioned PR got merged, did not have the chance to review.
[1] https:/
Just chipping in that I don't think we should add Pekko changes in a
patch release, because I think the Pekko related changes don't fix a
bug.
On Tue, Sep 19, 2023 at 9:06 PM Ferenc Csaky wrote:
>
> I think that is totally fine, because any Pekko related changes can only be
> added to the first
That is a fair point. It not fixes a bug per se, but it would mitigate security
vulnerabilities (Netty 3.x CVEs), so my thought was it might qualify it for
addressing in a patch release.
IMO handling security vulnerabilities is a gray area, if it only requires to
bump some deps that are only us
All the relatived changes have been merged,Which is mainly for CVEs, and there
are some changes relative to performance too.
Currently pekko only releases snapshot version, if you decide to contains it in
1.19， will need pekko1.1.0 to release before right?
On 2023/09/20 14:29:45 Ferenc Csaky
The related changes are :
https://github.com/apache/incubator-pekko/pull/643
https://github.com/apache/incubator-pekko/pull/651
https://github.com/apache/incubator-pekko/pull/652
https://github.com/apache/incubator-pekko/pull/656
It would be very helpful if you take another round of review, thanks
12 matches
Mail list logo
