-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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
[SPARK-50648][CORE] when the job is cancelled during shuffle retry in parent stage, might leave behind zombie running tasks #49270
base: master
Are you sure you want to change the base?
Changes from 1 commit
893fe64
a820cad
1bcd4b6
7fb4bc1
9a58f60
bc33ffb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -121,4 +121,6 @@ private[spark] trait TaskScheduler { | |
*/ | ||
def applicationAttemptId(): Option[String] | ||
|
||
|
||
def hasRunningTasks(stageId: Int): Boolean | ||
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. Why do we need this method ? 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. Please see this |
||
} |
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.
what if we just kill all waiting stages? Does
taskScheduler.killAllTaskAttempts
handle it well?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.
and can we add a special flag to indicate the waiting stages that are submitted due to retry?
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.
I tested: if the normally generated waiting stages call
killAllTaskAttempts
, the stage status will be displayed asFAILED
, which wasSKIPPED
before,killAllTaskAttempts
itself will not go wrong.Always kill waiting stage seems to be a safer approach (tasks really shouldn't be run anymore), but it may generate unnecessary
stageFailed
events compared with before.Yes, we can add a flag , please see the update codes.
Actually , there is a trade-off here to kill waiting stages, the range of choices from large to small :
stage#failedAttemptIds
> 0)stage#resubmitInFetchFailed
)