[
https://issues.apache.org/jira/browse/FLINK-29281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607600#comment-17607600
]
Claude Warren edited comment on FLINK-29281 at 9/23/22 9:07 AM:
----------------------------------------------------------------
I am working with a group of developers in an attempt to get an Akka fork
accepted as an Apache Project. If anyone here is interested in participating
in that project please reach out to me at cla...@apache.org
The repository that we are working from is at
https://github.com/mdedetrich/akka-apache We are looking for people who want to
participate as we start into the Apache incubator proecss
was (Author: claudenw):
I am working with a group of developers in an attempt to get an Akka fork
accepted as an Apache Project. If anyone here is interested in participating
in that project please reach out to me at cla...@apache.org
> Replace Akka
> ------------
>
> 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)
