Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2001#issuecomment-53911884
sc.stop in client mode isn't being called on the applicationMaster in
YarnClientSchedulerBackend, its called from the driver on the client/gateway
box.
The shutdownhook would be a final catch all though in case any weird
conditions happened.
I'm curious, what is the condition you are seeing where you need this?
As @vanzin said in the jira if its something that might affect other modes
perhaps it should be moved up higher.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
