merlimat commented on pull request #14320: URL: https://github.com/apache/pulsar/pull/14320#issuecomment-1041985838
> > We shouldn't add some temporary PRs during the release phase unless they are really important. > > @BewareMyPower This PR contains a very important change. The recommended maximum thread count for Jetty thread pool is 50-500. Pulsar current uses an invalid valid. @lhotari This is not a new thing and it's something that can easily be changed by users. I don't think we need to rush into a release. > The sync->async changes in the Pulsar Admin API are not needed when a proper value is used. The problem is not just keeping threads busy but the cases in which you have calls that spawn to multiple brokers. In this cases, the HTTP call can come back to same broker and we can have a deadlock, no matters how many threads we have in the pool. -- 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]
