-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-35402][WebUI] Increase the max thread pool size of jetty server in HistoryServer UI #32539
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
Conversation
This comment has been minimized.
This comment has been minimized.
|
Kubernetes integration test status failure |
|
Test build #138518 has finished for PR 32539 at commit
|
|
cc @cloud-fan @srowen @maropu @sarutak thanks |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #138536 has finished for PR 32539 at commit
|
|
Can we simply use different max threads num in live UI and history server UI? e.g. 200 for live UI and 1000 for history server UI? We still hardcode it and no need to add a config. |
yea, I will try |
|
Kubernetes integration test unable to build dist. exiting with code: 1 |
|
Test build #139079 has finished for PR 32539 at commit
|
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala
Outdated
Show resolved
Hide resolved
| port: Int) | ||
| extends WebUI(securityManager, securityManager.getSSLOptions("historyServer"), port, conf) | ||
| extends WebUI(securityManager, securityManager.getSSLOptions("historyServer"), | ||
| port, conf, poolSize = 1000) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can add a bit more comments to explain why history server needs a larger pool size.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW we can also set the name parameter properly as you did before.
|
Test build #139160 has finished for PR 32539 at commit
|
srowen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK, but let's update the title of this PR and JIRA then.
|
Kubernetes integration test starting |
|
Kubernetes integration test unable to build dist. exiting with code: 1 |
|
Kubernetes integration test status failure |
|
Kubernetes integration test starting |
|
Test build #139158 has finished for PR 32539 at commit
|
|
Kubernetes integration test status success |
|
thanks, @srowen, I've updated the content accordingly. |
|
Test build #139164 has finished for PR 32539 at commit
|
|
thanks, @srowen @cloud-fan for the review, merged to master for 3.2.0 |
What changes were proposed in this pull request?
For different UIs, e.g. History Server or Spark Live UI, maybe need different capabilities to handle HTTP requests. Usually, a History Server is for multi-users and needs more threads to increase concurrency, while Live UI is per application, which needn't that large pool size.
In this PR, we increase the max pool size of the History Server's jetty backend
Why are the changes needed?
increase the client concurrency of HistoryServer
Does this PR introduce any user-facing change?
no
How was this patch tested?
new tests