[SPARK-54832][UI] Spark executor page show driver gc times #53594
+4
−0
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
Member
|
Making driver's GC observable makes sense to me, but simply collecting to task GCs is a bit tricky to me |
Contributor
Author
hmm yea, add a new column in these two table? |
Member
|
I don't think it's eligible |
Contributor
Author
Any good suggestions? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Spark jobs driver side some times show below message
But Spark executor page didn't show driver GC metrics, When Driver GC is heavy, all executors may be waiting for scheduling, resulting in wasted resources. We need to optimize for heavy GC scenarios. We need to know this information very easily.
We can add it
Why are the changes needed?
To help users better understand their assignments
Does this PR introduce any user-facing change?
User can know driver side gc time in executors page
How was this patch tested?
Before
After
Was this patch authored or co-authored using generative AI tooling?
No