Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/5000#issuecomment-83150238
@jongyoul thanks for pointing out. `TASK_LOST` is already handled
[here](https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/CoarseMesosSchedulerBackend.scala#L280)
and
[here](https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala#L321).
I think what you really mean is to handle `TASK_ERROR` the same way as
`TASK_LOST`, right?
Currently the two backends don't behave the same way (`CoarseGrained`
considers both `TASK_FAILED` and `TAKS_LOST`, while the other one handles only
`TASK_LOST`). Maybe it makes sense to unify this too, maybe in a
`TaskState.isFailed` method.
---
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]
