GitHub user bingbai0912 opened a pull request:
https://github.com/apache/spark/pull/21891
[SPARK-24931][CORE]CoarseGrainedExecutorBackend send wrong 'Reason' wâ¦
TaskSetManager## What changes were proposed in this pull request?
When CoarseGrainedExecutorBackend find the executor not available, it will
send a "RemoveExecutor" message of "ExecutorExited" instead
"ExecutorLossReason". So it call tell driver whether is the executor
"exitCausedByApp" which should be false. So when dirver(TaskSetManager) can
"handleFailedTask" correctly to avoid task failed time up to the
"maxTaskFailures" and finally cause job failed.
## How was this patch tested?
tested in my own cluster
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bingbai0912/spark master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/21891.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 #21891
----
commit 3b3f224d6ac2dc3d3a0c21ed14502329af3cbae8
Author: baibing <baibing3@...>
Date: 2018-07-27T07:49:50Z
[SPARK-24931][CORE]CoarseGrainedExecutorBackend send wrong 'Reason' when
executor exits which leading to job failed.
----
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
