GitHub user devaraj-kavali opened a pull request:
https://github.com/apache/spark/pull/11996
[SPARK-10530] [CORE] Kill other task attempts when one taskattempt
belonging the same task is succeeded in speculation
## What changes were proposed in this pull request?
With this patch, TaskSetManager kills other running attempts when any one
of the attempt succeeds for the same task. Also killed tasks will not be
considered as failed tasks and they get listed separately in the UI and also
shows the task state as KILLED instead of FAILED.
## How was this patch tested?
core\src\test\scala\org\apache\spark\ui\jobs\JobProgressListenerSuite.scala
core\src\test\scala\org\apache\spark\util\JsonProtocolSuite.scala
I have verified this patch manually by enabling spark.speculation as true,
when any attempt gets succeeded then other running attempts are getting killed
for the same task and other pending tasks are getting assigned in those. And
also when any attempt gets killed then they are considered as KILLED tasks and
not considered as FAILED tasks. Please find the attached screen shots for the
reference.
Ref : https://github.com/apache/spark/pull/11916
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/devaraj-kavali/spark SPARK-10530
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/11996.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #11996
----
commit 1a9e36516e9016f43a605abce0ee49e1262363a6
Author: Devaraj K <[email protected]>
Date: 2016-03-28T09:03:07Z
[SPARK-10530] [CORE] Kill other task attempts when one taskattempt
belonging the same task is succeeded in speculation
----
---
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]
