[GitHub] spark issue #12436: [SPARK-14649][CORE] DagScheduler should not run duplicat...

[mridulm <gi...@git.apache.org>]

Github user mridulm commented on the issue:

    https://github.com/apache/spark/pull/12436
  
    
    I am curious how this is resilient to epoch changes which will be triggered due to executor loss for a shuffle task when its shuffle map task executor is gone.
    Wont it not create issues if we are trying to continue to (re)use the earlier stage @rxin @kayousterhout ?


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org