-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-26341][WEBUI]Expose executor memory metrics at the stage level, in the Stages tab #30573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
803921a
Executor metrics in stage level
AngersZhuuuu 55d520a
save
AngersZhuuuu 6d81362
fix ut
AngersZhuuuu 7dba885
follow comment
AngersZhuuuu 22c1e9e
Update stagepage.js
AngersZhuuuu 3070854
Update stagepage.js
AngersZhuuuu 6a32b44
Update stagepage.js
AngersZhuuuu 2725ffa
Merge branch 'master' into SPARK-26341
AngersZhuuuu a6dd5ab
solve conflicts
AngersZhuuuu 91a1f8e
fix UT
AngersZhuuuu b8d705b
Update stagepage.js
AngersZhuuuu cf4d3c4
Update stagepage.js
AngersZhuuuu e678f63
Update stagepage.js
AngersZhuuuu bf7ae7c
Merge branch 'master' into SPARK-26341
AngersZhuuuu 141fa27
Update webui.css
AngersZhuuuu 92cbcf7
fix end line
AngersZhuuuu e168193
remove option of peakMemoryMetrics
AngersZhuuuu 3cd21ce
Revert "remove option of peakMemoryMetrics"
AngersZhuuuu 13f6db2
follow comment
AngersZhuuuu 3cc3559
follow commnet
AngersZhuuuu fbd096a
save
AngersZhuuuu c85fd16
update
AngersZhuuuu ecd2779
Update stagepage.js
AngersZhuuuu c21be11
fix UT
AngersZhuuuu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm... executor metrics for each stage should be collected here.
But if the heartbeat interval from an executor is longer than lifetime of a stage, we can't collect the executor metrics for the stage.
So this change can be one option. What do you think @gengliangwang ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We collect all data to choose the peak metrics. IMO, more accuracy is better.
But I'm not particularly clear about the performance impact of this part, hope more suggestion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@imback82 Do you have any concern about this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems fine to me if we need more accurate peak values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that the first metrics of
peakExecutorMetricsbecome 0 instead of -1 after this. @AngersZhuuuu Do you know the reason?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-1is default peakExecutorMetrics, and with this change, we will update this value with real task metrics, but why all is0depend on the metrics data...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gengliangwang
By this change,
peakExecutorMetricsis updated not onlyonExecutorMetricsUpdatebut alsoonTaskEnd.So, the peak value carried by
SparkListenerTaskEndis0, the corresponding peak values inpeakExecutorMetricsis set to0.Do you have any concern?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sarutak No, I am ok with it :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
O.K, I'll merge later if there are no objections. Thanks for the response. @gengliangwang