On Thu, Feb 17, 2022 at 3:12 AM Yunze Xu <y...@streamnative.io.invalid> wrote:
> And we should make it clear whether numHttpServerThread=200 could
> solve the existing problem like
> https://github.com/apache/pulsar/pull/13666 
> <https://github.com/apache/pulsar/pull/13666>

Changing the number of threads won't do anything to improve the above
issue. The deadlock there is completely unrelated to the HTTP threads.

The Jetty thread getting stuck is just a side effect of the deadlock
caused by mixing sync & async operations.

Reply via email to