zhanghaou commented on PR #24383: URL: https://github.com/apache/pulsar/pull/24383#issuecomment-3265177836
> 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. Thank you for providing the additional information. I think it would be better to use a dedicated ForkJoinPool where necessary, instead of relying on the default common pool everywhere, even if the problem occurs, the impact will be relatively limited. -- 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]
