Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9982#issuecomment-161132945
Actually, here's a report which gives a more complete sense about the
frequency of this failing:
https://spark-tests.appspot.com/tests/org.apache.spark.streaming.BasicOperationsSuite/map#latest-failures
I've given it some thought and no longer think that we should introduce a
new state. The new state won't be necessary for tests and users who
interactively cancelled the StreamingContext.stop() are probably likely to turn
around and try to launch a new StreamingContext, in which case the existing
error message should be sufficient for them to know to retry. I'm going to roll
back the introduction of the new state and try to get this into merge-worthy
shape.
---
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]
