-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-17623][CORE] Clarify type of TaskEndReason with a failed task. #15181
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
2 commits
Select commit
Hold shift + click to select a range
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
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
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.
Is this totally safe? Can you point me to the code where we serialize 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.
Good question. its sent as an executor status update in various failure handling scenarios here, though its not so nicely grouped that its super-obvious they always go together, unfortunately:
https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/executor/Executor.scala#L357
I walked through the various cases and convinced myself they went together. I made one more minor improvement to make that more clear, a couple of
.toTaskEndReasonmethods could be renamed to.toTaskFailedReason(d991a3c).Really, though there were two other things that convinced me this was OK:
the only other possible thing a
TaskEndReasoncould be isSuccess. But you'll notice thatSuccessis never serialized as the msg -- its just implicit withTaskState.FINISHED, and then theSuccesspart just gets dropped in on the driver-side here:spark/core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala
Line 669 in 248922f
The TaskEndReason was already getting blind-casted before anyway:
spark/core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala
Line 710 in 248922f
This was already in the same thread, without any try/ catch etc. checks anyway. Well, except for this:
spark/core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala
Line 701 in 248922f
which I decided wasn't a concern mostly b/c of reason (1) again.
There's more cleanup we could do here:
TaskState.isFailedis unused, instead there is a different hard-coded check here:spark/core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala
Line 376 in 248922f
ExecutorBackend.statusUpdatewith more particular methods, so that the coupling is more explicit.and probably other related things too. If you have a strong preference, I could address those here, but figured it was best to just get in this small cleanup I felt confident in for now.
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.
great. It's always better to be more explicit