-
Notifications
You must be signed in to change notification settings - Fork 28.6k
[SPARK-1726] [SPARK-2567] Eliminate zombie stages in UI. #1566
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -710,7 +710,6 @@ class DAGScheduler( | |
if (missing == Nil) { | ||
logInfo("Submitting " + stage + " (" + stage.rdd + "), which has no missing parents") | ||
submitMissingTasks(stage, jobId.get) | ||
runningStages += stage | ||
} else { | ||
for (parent <- missing) { | ||
submitStage(parent) | ||
|
@@ -753,11 +752,14 @@ class DAGScheduler( | |
null | ||
} | ||
|
||
// must be run listener before possible NotSerializableException | ||
// should be "StageSubmitted" first and then "JobEnded" | ||
listenerBus.post(SparkListenerStageSubmitted(stageToInfos(stage), properties)) | ||
|
||
if (tasks.size > 0) { | ||
runningStages += stage | ||
// SparkListenerStageSubmitted should be posted before testing whether tasks are | ||
// serializable. If tasks are not serializable, a SparkListenerStageCompleted event | ||
// will be posted, which should always come after a corresponding SparkListenerStageSubmitted | ||
// event. | ||
listenerBus.post(SparkListenerStageSubmitted(stageToInfos(stage), properties)) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I also moved this event inside the check for tasks.size being > 0 -- because we shouldn't tell the UI/listeners about a stage if it doesn't have any tasks and therefore won't be run. |
||
|
||
// Preemptively serialize a task to make sure it can be serialized. We are catching this | ||
// exception here because it would be fairly hard to catch the non-serializable exception | ||
// down the road, where we have several different implementations for local scheduler and | ||
|
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
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.
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.
So just to clarify what's going on here: prior to my change, we added a stage to runningStages here, after calling submitMissingTasks (so after the code I modified below gets executed). This could lead to a memory leak (if the stage needed to be aborted in submitMissingTasks, due to a NotSerializableException for example, because then it would never be removed from runningStages). It also meant that the DAGScheduler sent a SparkListenerStageSubmitted event to the UI, but never a SparkListenerStageCompleted (because, on line 1072, we only send a SparkListenerStageCompleted event if the stage is in runningStages).