GitHub user jinxing64 opened a pull request:

    https://github.com/apache/spark/pull/16901

    [SPARK-19565] Improve DAGScheduler tests.

    ## What changes were proposed in this pull request?
    
    This is related to #16620. 
    When fetch failed, stage will be resubmitted. There can be running tasks 
from both old and new stage attempts. This pr added a test to check the case 
that success of tasks from old stage attempt should be taken as valid and 
partitionId should be removed from stage's pendingPartitions accordingly. When 
pending partitions is empty, downstream stage can be scheduled, even though 
there's still running tasks in the active(new) stage attempt.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jinxing64/spark SPARK-19565

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/16901.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 #16901
    
----
commit f5df21405f1eb31c7f32ffd7b32ed02abbc6d033
Author: jinxing <jinxing6...@126.com>
Date:   2017-02-12T12:39:53Z

    [SPARK-19565] Improve DAGScheduler tests.

----


---
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

Reply via email to