Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use at least 8 threads in Jetty thread pool #3776

Merged
merged 1 commit into from
Mar 7, 2019
Merged

Conversation

merlimat
Copy link
Contributor

@merlimat merlimat commented Mar 7, 2019

Motivation

Use at least 8 threads to avoid having Jetty go into threads starving and
having the possibility of getting into a deadlock where a Jetty thread is
waiting for another HTTP call to complete in same thread.

This solve the issues of requests timing out when the broker is making REST
calls to itself. Such examples are when running in standalone mode and
creating a function.

@merlimat merlimat added the type/bug The PR fixed a bug or issue reported a bug label Mar 7, 2019
@merlimat merlimat added this to the 2.3.1 milestone Mar 7, 2019
@merlimat merlimat self-assigned this Mar 7, 2019
@jerrypeng
Copy link
Contributor

rerun java8 tests

@massakam
Copy link
Contributor

massakam commented Mar 7, 2019

rerun java8 tests

1 similar comment
@massakam
Copy link
Contributor

massakam commented Mar 7, 2019

rerun java8 tests

@sijie sijie merged commit 7a9f7f3 into apache:master Mar 7, 2019
merlimat added a commit that referenced this pull request Mar 29, 2019
### Motivation

Use at least 8 threads to avoid having Jetty go into threads starving and
having the possibility of getting into a deadlock where a Jetty thread is
waiting for another HTTP call to complete in same thread.

This solve the issues of requests timing out when the broker is making REST
calls to itself. Such examples are when running in standalone mode and 
creating a function.
@merlimat
Copy link
Contributor Author

merlimat commented Apr 1, 2019

Merged in 2.3.1 at
49baf5d

sijie added a commit to sijie/pulsar that referenced this pull request May 26, 2019
fixes apache#4359

same as apache#3776

Use at least 8 threads to avoid having Jetty go into threads starving and
having the possibility of getting into a deadlock where a Jetty thread is
waiting for another HTTP call to complete in same thread.
merlimat pushed a commit that referenced this pull request May 28, 2019
fixes #4359

same as #3776

Use at least 8 threads to avoid having Jetty go into threads starving and
having the possibility of getting into a deadlock where a Jetty thread is
waiting for another HTTP call to complete in same thread.
@vicaya
Copy link
Contributor

vicaya commented Oct 31, 2019

Can we make the number of jetty threads configurable? Looks like it's impacting a bunch of other issues that involves admin tasks: #5417, #3877, #3878...

@merlimat
Copy link
Contributor Author

@vicaya That is already configurable. The only question was always what was the most conservative default value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants