GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/4118
Efficient way to deal with ExecutorLost
Currently, the handler of the case when an executor being lost in
DAGScheduler (`handleExecutorLost`) looks not efficient. This pr tries to add a
bit of extra information to Stage class to improve that.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/viirya/spark-1 efficient_failed
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/4118.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 #4118
----
commit 161758c5fef79f3c1000cb30a6532674514149cd
Author: Liang-Chi Hsieh <[email protected]>
Date: 2015-01-20T09:46:44Z
Efficient way to deal with ExecutorLost.
----
---
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]
