Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15986#discussion_r89417124
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -525,7 +525,12 @@ private[spark] class TaskSchedulerImpl(
* of any running tasks, since the loss reason defines whether we'll
fail those tasks.
--- End diff --
> Is it possible for anything to go awry for task updates that happen
between the first removeExecutor call ... and when the task is marked as failed
If there's something really wrong with the YARN AM, it can take some time,
but eventually the second call will come, either with the actual reason or with
a generic "executor lost" reason. This is handled in
`YarnSchedulerEndpoint.handleExecutorDisconnectedFromDriver`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
