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

[SPARK-50381][CORE] Support spark.master.rest.maxThreads #48921

Closed
wants to merge 1 commit into from

Conversation

dongjoon-hyun
Copy link
Member

@dongjoon-hyun dongjoon-hyun commented Nov 21, 2024

What changes were proposed in this pull request?

This PR aims to support spark.master.rest.maxThreads.

Why are the changes needed?

To provide users a way to control the number of maximum threads of REST API. Previously, Apache Spark uses a default constructor whose value is fixed to 200 always.

https://github.com/jetty/jetty.project/blob/5dfc59a691b748796f922208956bd1f2794bcd16/jetty-util/src/main/java/org/eclipse/jetty/util/thread/QueuedThreadPool.java#L118-L121

Does this PR introduce any user-facing change?

No, the default value of new configuration is identical with the previously-used Jetty's default value.

How was this patch tested?

Pass the CIs with a newly added test case.

Was this patch authored or co-authored using generative AI tooling?

No.

@dongjoon-hyun
Copy link
Member Author

The newly added UT passed already in the CIs.

[info] - SPARK-50381: Support spark.master.rest.maxThreads (15 milliseconds)

.doc("Maximum number of threads to use in the Spark Master REST API Server.")
.version("4.0.0")
.intConf
.createWithDefault(200)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default value is identical with the previously-used Jetty's default value.

@dongjoon-hyun
Copy link
Member Author

Thank you, @viirya !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants