Fix: should not add emptyDir sizeLimit conf on executor pods if it is nil #2316
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.
Purpose of this PR
Proposed changes:
This is a follow up fix from work already done in #2305 by @ChenYi015
This PR adds a check at submission on executors pods if an emptyDir
sizeLimit
isnil
.Change Category
Rationale
Following some further testing of an older
SparkApplication
template wherein the volumeName (see issue #2199 for more details) had not been changed, I noticed behaviour wherein only the driver pod would get created and no executor pods would spawn. I believe this is due to the same issue outlined in #2305 which would make sense, as the check was only added on the driver pod submission, and not the executors.Checklist
Additional Notes