[
https://issues.apache.org/jira/browse/SPARK-10911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036613#comment-15036613
]
Marcelo Vanzin commented on SPARK-10911:
----------------------------------------
Ok, that makes sense. But since the YARN bug is the source of the problem here,
the commit message (and maybe even the code) should mention it.
> Executors should System.exit on clean shutdown
> ----------------------------------------------
>
> Key: SPARK-10911
> URL: https://issues.apache.org/jira/browse/SPARK-10911
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 1.5.1
> Reporter: Thomas Graves
> Assignee: Zhuo Liu
> Priority: Minor
>
> Executors should call System.exit on clean shutdown to make sure all user
> threads exit and jvm shuts down.
> We ran into a case where an Executor was left around for days trying to
> shutdown because the user code was using a non-daemon thread pool and one of
> those threads wasn't exiting. We should force the jvm to go away with
> System.exit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
