Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/11692
Wow this is old. @WangTaoTheTonic I'm not sure this is the right fix. The
code in YarnClientSchedulerBackend is already catching InterruptedException:
```
try {
val (state, _) = client.monitorApplication(appId.get,
logApplicationReport = false)
logError(s"Yarn application has already exited with state $state!")
allowInterrupt = false
sc.stop()
} catch {
case e: InterruptedException => logInfo("Interrupting monitor
thread")
}
```
It seems it just needs to be tweaked to also handled the
`UndeclaredThrowableException` case.
---
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]
