Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/11692#issuecomment-196889060
hi @tgravescs , it happened when sc stop normally in client mode. As
sc.stop will stop dagscheduler -> stop taskscheduler -> stop scheduler backend
-> interrupt the monitor thread, the monitor thread will enter into a retry
logic in which there is a sleep intervals(which is not the sleep
[here](https://github.com/WangTaoTheTonic/spark/blob/SPARK-13852/yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala#L970))
waiting for RM's switching.
The sleep methods will throw an InterruptedException when it is
interrupted, so we need to catch it because it will log the application failed
as treated as NonFatal(e).
---
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]
