GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/2865
[SPARK-4020] Do not rely on timeouts to remove failed block managers
If an executor fails without being scheduled to run any tasks, then
`DAGScheduler` won't notify `BlockManagerMasterActor` that the associated block
manager should be removed. Instead, the associated block manager will be
expired only after a few rounds of heartbeat timeouts.
In terms of removal treatment, there should really be no distinction
between executors that have been scheduled tasks and those that have not. The
fix, then, is to add all known executors to `TaskSchedulerImpl`'s
`activeExecutorIds` whether or not it has been scheduled a task.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewor14/spark active-executors
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/2865.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 #2865
----
commit fd99616aea33a4abaccdf74b23f4794dcbb408b7
Author: Andrew Or <[email protected]>
Date: 2014-10-20T23:51:50Z
Add all known executors to `activeExecutorIds`
----
---
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]
