Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/4474#issuecomment-95907922
@pwendell i think we cannot kill JVM directly when this occurs. when it is
hive server that one driver for many jobs, if we kill JVM, other jobs on this
driver cannot continue. i think this pr is ok that just abort this job and then
DAGScheduler will throw a jobFailed exception to client. if it is hive server,
then hive server can catch this exception and continue to run other jobs. if it
is a application that i said, user application donot catch this exception and
throw this to applicationMaster, then application will be failed. so that can
ensure that is be right for any situations.
---
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
