[scheduler] pekko integration #1032
Conversation
| import scala.concurrent.Promise | ||
| import scala.concurrent.duration.* | ||
|
|
||
| class KyoExecutorServiceConfiguratorTest |
There was a problem hiding this comment.
@He-Pin I think the last time I used Akka/Pekko was a decade ago :) Does it have custom locals/threadlocals that we need to check for propagation like in Finagle's integration?
| val actor = system.actorOf(Props(new Actor { | ||
| def receive = { | ||
| case _ => | ||
| executorThread = Thread.currentThread() |
There was a problem hiding this comment.
better with an ask/? and reply with the thread name,eg : apache/pekko#1728
| case msg => | ||
| threadNames.synchronized { | ||
| threadNames += Thread.currentThread().getName | ||
| } |
There was a problem hiding this comment.
just sender ! Thread.currentThread().getName
| * [[org.apache.pekko.dispatch.ExecutorServiceConfigurator]] for the Pekko dispatcher interface | ||
| */ | ||
| class KyoExecutorServiceConfigurator(config: Config, prerequisites: DispatcherPrerequisites) | ||
| extends ExecutorServiceConfigurator(config, prerequisites) { |
There was a problem hiding this comment.
can we configure the Kyo scheduler in detail? Seems it's just using the default one.
There was a problem hiding this comment.
Kyo's scheduler is designed to work as a JVM-global resource so it doesn't allow creating separate instances. It has several configs that can be set via system properties but I'd recommend trying the defaults first.
Co-authored-by: Ondra Pelech <[email protected]>
|
/release |
Fixes #1028