Repository navigation
fix: size the native runtime for standalone executors without spark.executor.cores #6368
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
Merged
andygrove
merged 5 commits into
apache:main
from
andygrove:tokio-workers-standalone-cores
Oct 18, 2026
+126
−23
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3cb4a3d
fix: size the native runtime for standalone executors without spark.e…
andygrove c68955a
Merge remote-tracking branch 'apache/main' into tokio-workers-standal…
andygrove 0561c6a
address review: fall back to available processors for unknown masters…
andygrove 248a8f9
Merge remote-tracking branch 'apache/main' into tokio-workers-standal…
andygrove 49219ad
style: apply spotless
andygrove File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
For an unknown master this still starts a single worker, which is the situation in #6292. For
mesos://on Spark 3.x, an executor withoutspark.executor.corestakes the cores of the offer (MesosCoarseGrainedSchedulerBackend.executorCoresin v3.5.8), which is similar to standalone. WouldavailableProcessorsbe a safer fallback than 1 here? I'd expect a few idle Tokio threads to cost less than starving concurrent tasks, but I haven't measured that or looked at other external cluster managers.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.
Agreed, and I checked the Mesos case: on Spark 3.x an executor without
spark.executor.corestakes the cores of the offer, as a standalone one does. An unknown master now falls back toavailableProcessorsand still logs the warning once. The tuning guide says why: a few idle workers cost less than too few.