Github user artemrd commented on the issue:
https://github.com/apache/spark/pull/21114
This issue is more like a race condition, so the test needs to generate a
specific sequence of events to reproduce the issue. I agree it's probably too
specific. What is Spark approach to reproduce this kind of issues?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
