[SPARK-54813] Remove cores configs from tests/e2e/watched-namespaces/spark-example.yaml
#443
Conversation
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
dongjoon-hyun
force-pushed
the
SPARK-54813
branch
2 times, most recently
from
904c54b to
2d4c50b
Compare
…es/spark-example.yaml`
dongjoon-hyun
force-pushed
the
SPARK-54813
branch
from
2d4c50b to
39bf15b
Compare
Member
Author
|
Since this is a test-only change, let me merge this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
This PR aims to simplify
tests/e2e/watched-namespaces/spark-example.yamlby removing irrelevantspark.kubernetes.*.request.coresconfigs and adding relevantSpark Operatorconfiguration explicitly.Why are the changes needed?
The main consumer of CPU resources is
Spark Operatorinstead ofSpark Application. We had better explicitly setSpark OperatorCPU core request.Does this PR introduce any user-facing change?
No behavior change.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.