dynamic allocation executor pending for addition flood fix #396
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
|
@kira-lin Can you please take a look at this |
|
Sorry for the late reply. I have a question: do you mean that the executors killed by Spark due to dynamic resource allocation will try to restart? |
With dynamic resource allocation the amount of pending executor creation is way greater than actual number of executor , so even after completion of spark job the executor is alive for much longer |
|
@kira-lin Can you help with the review and merge? |
kira-lin
approved these changes
Apr 9, 2024
carsonwang
pushed a commit
that referenced
this pull request
Jun 26, 2024
* dynamicallocation executor pending for addition flood fix * scala checkstyle fix * scala checkstyle fix * scala checkstyle fix
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.
Overview
Issue :
Currently with dynamic allocation for executors there are too many executors pending to be added while the actual number of max executor is far less
Solution:
This will check with dynamic auto scale no additional pending executor actor added more than max executors count
as this result in executor even running after job completion