Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/11720#discussion_r57581491
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -286,6 +286,7 @@ class DAGScheduler(
case None =>
// We are going to register ancestor shuffle dependencies
getAncestorShuffleDependencies(shuffleDep.rdd).foreach { dep =>
+ assert(!shuffleToMapStage.get(dep.shuffleId).isDefined)
--- End diff --
Why are you asserting this when you are already within a match case where
this must be true? If it is actually possible for the contents of
shuffleToMapStage to change between the pattern match and the foreach, then we
need to fix the unsynchronized update, not just shutdown Spark on a failed
assertion.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
