[
https://issues.apache.org/jira/browse/FLINK-23091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367503#comment-17367503
]
Etienne Chauchot commented on FLINK-23091:
------------------------------------------
One extra comment: migration from version 2.5.21 that we currently use to 2.6.x
(latest 2.6.15 I guess) should not be too painful as the releases are binary
backward compatible:
[https://doc.akka.io/docs/akka/current/project/migration-guide-2.5.x-2.6.x.html]
That being said, there is still something that could be a problem: akka 2.6 is
available only on scala 2.12. Flink supports scala 2.12 but the build profile
expects to use the same akka version between scala 2.11 and scala 2.12 as in
replaces only _scala.version_ suffixes (and disables unavailable tests in scala
2.12 env) and akka 2.5.21_scala2.12 does not exist. So I think we would need to
change the current scala 2.12 build profile to something more complex to
address this case of having 2 different akka versions depending on the chosen
scala version.
> Bump Akka to 2.6
> ----------------
>
> Key: FLINK-23091
> URL: https://issues.apache.org/jira/browse/FLINK-23091
> Project: Flink
> Issue Type: Sub-task
> Components: Build System, Runtime / Coordination
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Fix For: 1.14.0
>
>
> When loading akka 2.5 through a separate classloader a leak occurs because
> akka 2.5 contains a custom ForkJoinPool implementation with a ThreadLocal,
> which results in a ClassLoaderLeak if any outside thread touches this
> implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
