psavalle opened a new pull request, #56926:
URL: https://github.com/apache/spark/pull/56926
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
This is a first attempt at
[SPARK-49580](https://issues.apache.org/jira/browse/SPARK-49580?jql=project%20%3D%20SPARK%20AND%20component%20%3D%20%22Connect%22%20AND%20text%20~%20%22concurrent%22),
adding a maximum number of concurrent executions.
### Why are the changes needed?
With Spark Connect, it is more common to have many users running possibly
many queries concurrently against a single driver, and it would be useful to
have some control over the maximum number of executions that can occur.
### Does this PR introduce _any_ user-facing change?
Yes, new configuration parameters:
- `spark.connect.execute.maxConcurrentQueries`: maximum number of concurrent
queries that can be executed. When this limit is reached, new queries will wait
in a queue until a slot becomes available. Set to 0 or negative to disable the
limit (unlimited concurrency). This only affects Spark Connect executions.
- `spark.connect.execute.maxConcurrentQueries.timeout`: aximum time a query
waits for an execution slot when
<code>spark.connect.execute.maxConcurrentQueries</code> is reached. Waiters are
served in FIFO order. If a slot does not become available within this time, the
query fails with a retryable error so the client re-submits it. Set to 0 to
wait indefinitely.
Note: maybe 'maxConcurrentExecutions' would be more precise here? Not sure
what the best naming would be.
### How was this patch tested?
Added tests, will do more testing once we confirm the plan makes sense.
### Was this patch authored or co-authored using generative AI tooling?
Yes, modified changes provided by Claude.
Generated-by: 2.1.159 (Claude Code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
