[jira] [Commented] (FLINK-29281) Replace Akka by gRPC-based RPC implementation

["Ferenc Csaky (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-29281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747530#comment-17747530 ] 

Ferenc Csaky commented on FLINK-29281:
--------------------------------------

[~chesnay] is this annulates the Akka Artery migration (FLINK-28372) at this point? Now that the migration to Pekko is done, which is an Akka 2.6 fork, which does not change the semantics of the Artery migration I guess, but if this is in reach, putting more effort into Artery and update/complete the existing draft may not worth it.

> Replace Akka by gRPC-based RPC implementation
> ---------------------------------------------
>
>                 Key: FLINK-29281
>                 URL: https://issues.apache.org/jira/browse/FLINK-29281
>             Project: Flink
>          Issue Type: Technical Debt
>          Components: Runtime / RPC
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>
> Following the license change I propose to eventually replace Akka.
> Based on LEGAL-619 an exemption is not feasible, and while a fork _may_ be created it's long-term future is up in the air and I'd be uncomfortable with relying on it.
> I've been experimenting with a new RPC implementation based on gRPC and so far I'm quite optimistic. It's also based on Netty while not requiring as much of a tight coupling as Akka did.
> This would also allow us to sidestep migrating our current Akka setup from Netty 3 (which is affected by several CVEs) to Akka Artery, both saving work and not introducing an entirely different network stack to the project.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)