You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/04/01 19:02:55 UTC
[jira] [Assigned] (SPARK-6650) ExecutorAllocationManager never
stops
[ https://issues.apache.org/jira/browse/SPARK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-6650:
-----------------------------------
Assignee: Apache Spark
> ExecutorAllocationManager never stops
> -------------------------------------
>
> Key: SPARK-6650
> URL: https://issues.apache.org/jira/browse/SPARK-6650
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.3.0
> Reporter: Marcelo Vanzin
> Assignee: Apache Spark
>
> {{ExecutorAllocationManager}} doesn't even have a stop() method. That means that when the owning SparkContext goes away, the internal thread it uses to schedule its activities remains alive.
> That means it constantly spams the logs and does who knows what else that could affect any future contexts that are allocated.
> It's particularly evil during unit tests, since it slows down everything else after the suite is run, leaving multiple threads behind.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org