Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/17113
@squito Correct, we really only try to kill running tasks currently on job
failure (and if the config setting allows it); but there is the long-standing
"TODO: Cancel running tasks in the stage" in `case FetchFailed` of
`DAGScheduler#handleTaskCompletion`, which has languished as a TODO both
because resolving it would require us both to make Spark itself handle task
interruption in the fetch failure case and to deal with the same issues
preventing us from making task interruption the default even for job
cancelation.
All I'm really saying is that we shouldn't design in a hard requirement
that tasks cannot be interrupted (on job cancelation, fetch failure or some
other event), because we'd often really like to be able to kill running tasks
-- even though we don't know quite how to do that safely right now.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
