Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14557
---
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 shenh062326 commented on a diff in the pull request:
https://github.com/apache/spark/pull/14557#discussion_r74714601
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -798,6 +798,19 @@ private[spark] class TaskSetManager(
}
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/14557#discussion_r74688576
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -798,6 +798,19 @@ private[spark] class TaskSetManager(
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/14557#discussion_r74688557
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -798,6 +798,19 @@ private[spark] class TaskSetManager(
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/14557#discussion_r74688550
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -798,6 +798,19 @@ private[spark] class TaskSetManager(
Github user shenh062326 commented on a diff in the pull request:
https://github.com/apache/spark/pull/14557#discussion_r74021599
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -1564,6 +1564,14 @@ class SparkContext(config: SparkConf) extends
Logging with
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/14557#discussion_r74017373
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -1564,6 +1564,14 @@ class SparkContext(config: SparkConf) extends
Logging with
GitHub user shenh062326 opened a pull request:
https://github.com/apache/spark/pull/14557
[SPARK-16709][CORE] Kill the running task if stage failed
## What changes were proposed in this pull request?
At SPARK-16709, when a stage failed, but the running task is still
