Replies: 4 comments 11 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
you can also add custom dispatchers if you want to just solve this problem for yourself and not worry about patching this in Pekko - https://gist.github.com/yanns/f7da61c582ab1da3535d is an example |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply! My project is still on Akka 2.6.20 and migration to Pekko won't happen soon so all of this is not of immediate importance for Pekko and me. My question was more about current state and the future plans for JDK version support. |
Beta Was this translation helpful? Give feedback.
-
|
Dropping Java 8 support is not a big priority for us - there are pros and cons. The biggest con is that many users still use Java 8. I raised #483 anyway - for a solution to this problem that doesn't involve removing Java 8 support. |
Beta Was this translation helpful? Give feedback.
-
|
I understand. Thank you for your time! |
Beta Was this translation helpful? Give feedback.
-
|
@migesok I have a PR associated with #483 but it is awkward to write using Java reflection and hard to unit test due to the order in which the Pekko build runs. In the end of the day, we should consider fixing it so that users can use the custom dispatchers everywhere in Pekko. Would you be able to provide specific examples of where you are forced to use to use the default fork-join-executor? At some point, users are going to want Project Loom based executors, for instance. |
Beta Was this translation helpful? Give feedback.
-
|
The JDK 8, which was released almost a decade ago, is quite old. Would you like to continue supporting it? In my humble opinion, it would be wise to switch to the newer JVM. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, there are people who think we should support Java 8 still and Java 8 still gets security patches - so it is viable for users to stick with it. |
Beta Was this translation helpful? Give feedback.
-
|
We just starting to migrate from JDK 8 to JDK 11, slow progress... |
Beta Was this translation helpful? Give feedback.
-
|
Akka just dropped JDK 8. Will pekko drop JDK 8 in pekko 1.2.x? |
Beta Was this translation helpful? Give feedback.
-
Most likely not, there are a lot of people that use JDK 1.8. What's more likely is that we will start doing multi release jars so we can use functionality in newer JDKs |
Beta Was this translation helpful? Give feedback.
-
|
I haven't been able to find any information from the discussions recently so I am commenting on this one. My team can't move to java 11 until 2026 and we are currently migrating away from Play due to that constraint. Does it look like Pekko will at least support security updates for java 8 -compatible versions for a few more years? |
Beta Was this translation helpful? Give feedback.
-
|
We still support Java 8 for all releases. Even when we drop Java 8 support, we will backport security fixes to older release lines. |
Beta Was this translation helpful? Give feedback.
-
|
Ah ok thank you that is good to know. Looks like we are switching to pekko then. |
Beta Was this translation helpful? Give feedback.
-
|
And if you find any, you can report or contribute too, it's open-source |
Beta Was this translation helpful? Give feedback.
-
Hi!
May be I'm wrong but seems that Pekko does still support building and running on Java 8. Would you consider in the future raising the minimal JDK version requirement to at least 11?
I have a fix to contribute in the ForkJoinExecutorConfigurator but it relies on Java 9+ features of the ForkJoinPool, namely maximumPoolSize constructor parameter.
In a nutshell the problem is that during periods of prolonged CPU starvation, an Akka app (cluster + http) might slowly create more and more idle threads in the default pool until it becomes unresponsive or dies with OOM. Currently ForkJoinExecutorConfigurator does not specify maximumPoolSize which makes the pool effectively unbounded. We can use the default JDK common pool strategy there - parallelism + max spare threads count (default: 256) with the max spare threads count configurable.
Beta Was this translation helpful? Give feedback.
All reactions