feat: Add option to limit number of executor worker threads #1139
Conversation
This file contains 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
|
there is also |
|
will open another PR to remove |
milenkovicm
force-pushed
the
feat_executor_threads
branch
from
6e0407b
to
94359f7
Compare
this option is similar to `spark.executor.cores` it sets number of tokio worker threads.
milenkovicm
force-pushed
the
feat_executor_threads
branch
from
94359f7
to
fd6b75f
Compare
|
this PR may make no sense as there is dedicated executor which has limited number of runners |
|
DedicatedExecutor will limit number of threads based on |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
executor_coresconfiguration option is similar tospark.executor.cores, it sets number of tokio worker threads limiting executor cpu utilisation.Which issue does this PR close?
Closes none .
Rationale for this change
provide ability to users to limit number of cores which executor can utilise limiting overall resource utilisation
What changes are included in this PR?
Are there any user-facing changes?
new configuration option exposed to user