Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3143#issuecomment-62214013
> the current pattern allows someone calling sc.stop() to terminate this
thread cleanly, independent of what YARN says
It looks like `stop()` calls `client.stop()`, which could implement the
volatile variable to interrupt any threads that called `monitorApplication`.
So, it sounds like we'll probably end up implementing the `@volatile` in either
case, but I'm suggesting that this synchronization / interruption logic should
be hidden inside the `Client` rather than exposed here.
---
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]
