[ https://issues.apache.org/jira/browse/SPARK-14513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-14513: ------------------------------------ Assignee: Apache Spark > Threads left behind after stopping SparkContext > ----------------------------------------------- > > Key: SPARK-14513 > URL: https://issues.apache.org/jira/browse/SPARK-14513 > Project: Spark > Issue Type: Bug > Components: Spark Core > Affects Versions: 1.6.1 > Reporter: Terence Yim > Assignee: Apache Spark > > After {{SparkContext}} is stopped, there are couple threads that are left > behind. After some digging it is caused by couple bugs: > 1. The {{HttpBasedFileServer.shutdown()}} is not getting called during > {{NettyRpcEnv.shutdown()}}, hence a thread is left and block on the > {{ServerSocket.accept()}} from the underlying Jetty {{Server}}. > 2. {{QueuedThreadPool}} created in the {{HttpServer}} and through the > {{JettyUtils.startJettyServer}} method are never getting stopped. This is due > to the fact that thread pool used by Jetty {{Server}} won't get closed > automatically when the {{Server}} is stopped. > I'll send out a patch soon. -- 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