Skip to content

Conversation

@yaooqinn
Copy link
Member

@yaooqinn yaooqinn commented May 13, 2021

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

@SparkQA

This comment has been minimized.

@SparkQA
Copy link

SparkQA commented May 13, 2021

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43039/

@SparkQA
Copy link

SparkQA commented May 13, 2021

Test build #138518 has finished for PR 32539 at commit 19bf355.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@yaooqinn
Copy link
Member Author

cc @cloud-fan @srowen @maropu @sarutak thanks

@yaooqinn yaooqinn self-assigned this May 14, 2021
@SparkQA
Copy link

SparkQA commented May 14, 2021

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43057/

@SparkQA
Copy link

SparkQA commented May 14, 2021

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43057/

@SparkQA
Copy link

SparkQA commented May 14, 2021

Test build #138536 has finished for PR 32539 at commit 37a168a.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@cloud-fan
Copy link
Contributor

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.

@yaooqinn
Copy link
Member Author

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

@SparkQA
Copy link

SparkQA commented May 29, 2021

Kubernetes integration test unable to build dist.

exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43600/

@SparkQA
Copy link

SparkQA commented May 29, 2021

Test build #139079 has finished for PR 32539 at commit fecbb42.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

port: Int)
extends WebUI(securityManager, securityManager.getSSLOptions("historyServer"), port, conf)
extends WebUI(securityManager, securityManager.getSSLOptions("historyServer"),
port, conf, poolSize = 1000)
Copy link
Contributor

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.

Copy link
Contributor

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.

@SparkQA
Copy link

SparkQA commented Jun 1, 2021

Test build #139160 has finished for PR 32539 at commit 21a799a.

  • This patch fails to build.
  • This patch merges cleanly.
  • This patch adds no public classes.

Copy link
Member

@srowen srowen left a 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.

@SparkQA
Copy link

SparkQA commented Jun 1, 2021

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43677/

@SparkQA
Copy link

SparkQA commented Jun 1, 2021

Kubernetes integration test unable to build dist.

exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43679/

@SparkQA
Copy link

SparkQA commented Jun 1, 2021

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43677/

@SparkQA
Copy link

SparkQA commented Jun 1, 2021

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43684/

@SparkQA
Copy link

SparkQA commented Jun 1, 2021

Test build #139158 has finished for PR 32539 at commit d6a27df.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Jun 1, 2021

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43684/

@yaooqinn yaooqinn changed the title [SPARK-35402][WebUI] Make thread pool of jetty server in Web UIs configurable [SPARK-35402][WebUI] Increase the max thread pool size of jetty server in HistoryServer UI Jun 1, 2021
@yaooqinn
Copy link
Member Author

yaooqinn commented Jun 1, 2021

thanks, @srowen, I've updated the content accordingly.

@SparkQA
Copy link

SparkQA commented Jun 1, 2021

Test build #139164 has finished for PR 32539 at commit 065ddce.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@yaooqinn yaooqinn closed this in a127d91 Jun 1, 2021
@yaooqinn
Copy link
Member Author

yaooqinn commented Jun 1, 2021

thanks, @srowen @cloud-fan for the review, merged to master for 3.2.0

@yaooqinn yaooqinn deleted the SPARK-35402 branch June 1, 2021 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants