GitHub user jiangxb1987 opened a pull request:
https://github.com/apache/spark/pull/18362
[SPARK-20832][Core] Standalone master should explicitly inform drivers of
worker deaths and invalidate external shuffle service outputs
## What changes were proposed in this pull request?
In standalone mode, master should explicitly inform each active driver of
any worker deaths, so the invalid external shuffle service outputs on the lost
host would be removed from the shuffle mapStatus, thus we can avoid future
`FetchFailure`s.
## How was this patch tested?
Manually tested by the following steps:
1. Start a standalone Spark cluster with one driver node and two worker
nodes;
2. Run a Job with ShuffleMapStage, ensure the outputs distribute on each
worker;
3. Run another Job to make all executors exit, but the workers are all
alive;
4. Kill one of the workers;
5. Run rdd.collect(), before this change, we should see `FetchFailure`s and
failed Stages, while after the change, the job should complete without failure.
Before the change:
After the change:
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jiangxb1987/spark removeWorker
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/18362.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 #18362
----
commit 6369af0792bb3439d061f5a9ac279c87d39b4d06
Author: Xingbo Jiang <[email protected]>
Date: 2017-06-19T14:04:52Z
on WorkerRemoved, invalidate the outputs on the host from MapStatus.
commit 825ade06bd47fd201ee90fa28b78b951049cf7a4
Author: Xingbo Jiang <[email protected]>
Date: 2017-06-19T14:27:56Z
update
commit fb72fb6ea8dc02753d8c699f985afc70d1ccd971
Author: Xingbo Jiang <[email protected]>
Date: 2017-06-20T10:16:50Z
remove output from shuffle status
----
---
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]
