Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/21577
I think Ryan's change might still be good to introduce (i.e. a change that
replaces the attempt id in that code with something a little more unique),
regardless of any fix here.
The unit tests I added artificially re-creates the calls that would lead to
the situation, but I haven't tried to create a test case that would run things
through the scheduler.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
