lhotari commented on PR #24383: URL: https://github.com/apache/pulsar/pull/24383#issuecomment-3265049506
> For users deploying with Docker, this might be helpful. However, many users are likely installing the JDK themselves and running Pulsar directly on a VM. As for the JDK version, it seems we only specify the major version requirement, without detailing the minor versions. For users installing the JDK directly, it's even easier to use Java 21.0.8 for Pulsar 3.0.x > The version we maintain internally has removed all dependencies on the ForkJoin Pool, including the content mentioned in this PR, as well as the caffeine part (since asynchronous construction in caffeine also uses the ForkJoinPool by default). Well, that's one way to have a workaround to the JVM bug. > Given the current situation, I think this PR is meaningful. That's true. However, replacing all usages of ForkJoinPool in Pulsar might not make sense. ForkJoinPool is useful in certain cases due to the ability to add more threads when all threads are blocked and work cannot progress because of that. For example, IIRC, that addresses some deadlock scenarios when ExtensibleLoadManager is used. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
