You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/09/13 11:17:00 UTC
[jira] [Updated] (FLINK-29281) Replace Akka

     [ https://issues.apache.org/jira/browse/FLINK-29281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler updated FLINK-29281:
-------------------------------------
    Description: 
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.

  was:
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.


> 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)