Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17208
Looks good. Expanding on Imran's comment, how about:
We must set the taskset to zombie before the DAGScheduler handles the
taskEnded event. It's possible the taskEnded event will cause the DAGScheduler
to launch a new stage attempt (this happens when map output data was lost), and
if this happens before the taskSet has been set to zombie, it will appear that
we have conflicting task sets.
---
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
