Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7846#issuecomment-126882682
Is the sequence that `sc.stop` causes the backend to stop which may
interrupt the monitor thread, which may be the thing causing it to stop? This
change doesn't stop this sequence from happening though; there's still a race
condition. Why would the thread interrupt itself as the last thing it does?
This is cleaner if it's entirely local to the monitor thread. The backend
doesn't need a new field for this. The thread can have a "stop" method that
interrupts it only if it's blocked in `monitorApplication`.
---
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]
