Marcelo Vanzin created SPARK-6650:
-------------------------------------
Summary: 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
{{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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
