Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
If StreamingContext.stop() is interrupted midway through the call, the context will be marked as stopped but certain state will have not been cleaned up. Because the stopped flag will be set, subsequent stop() calls will be unable to finish stopping the context, preventing any new StreamingContexts from being created.
We should mitigate this race condition by ensuring that the second stop() call is able to clean up the partially-stopped context.