Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2127#issuecomment-53518853
@kayousterhout I looked into the racing condition we discussed offline. I
think even in that case the scheduler is resilient.
If you look at `newOrUsedStage`, it gets the map output locs from
MapOutputTracker this way:
```scala
val serLocs =
mapOutputTracker.getSerializedMapOutputStatuses(shuffleDep.shuffleId)
val locs = MapOutputTracker.deserializeMapStatuses(serLocs)
for (i <- 0 until locs.size) {
stage.outputLocs(i) = Option(locs(i)).toList // locs(i) will be
null if missing
}
```
The Option there guards against null locations.
---
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]
