Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17485
---
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
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/17485#discussion_r109174578
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -768,6 +767,19 @@ private[spark] class TaskSetManager(
Github user sitalkedia commented on a diff in the pull request:
https://github.com/apache/spark/pull/17485#discussion_r109067135
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -768,6 +767,19 @@ private[spark] class TaskSetManager(
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/17485#discussion_r109038854
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -768,6 +767,19 @@ private[spark] class TaskSetManager(
GitHub user sitalkedia opened a pull request:
https://github.com/apache/spark/pull/17485
[SPARK-20163] Kill all running tasks in a stage in case of fetch failure
## What changes were proposed in this pull request?
Currently, the scheduler does not kill the running tasks in
