GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/15176
[SPARK-17610][CORE][SCHEDULER]The failed stage caused by FetchFailed may
never be resubmitted
## What changes were proposed in this pull request?
The improper time order in handling failed task caused by FetchFailed may
cause corresponding stage not being resubmitted ever. For details, see:
https://issues.apache.org/jira/browse/SPARK-17610
## How was this patch tested?
manual tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/WangTaoTheTonic/spark SPARK-17610
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/15176.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 #15176
----
commit 910fd71bb9503c442817c04324f0843574c44fd5
Author: WangTaoTheTonic <wangtao...@huawei.com>
Date: 2016-09-21T07:29:28Z
The failed stage caused by FetchFailed may never be resubmitted
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
