[
https://issues.apache.org/jira/browse/SPARK-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193747#comment-14193747
]
Patrick Wendell commented on SPARK-4180:
----------------------------------------
Yeah [~adav] just ran into an issue where a lot of our tests weren't properly
cleaning SparkContext's and it was a huge pain. We could also log the callsite
where a SparkContext is created, so if you try to create another one it
actually tells you where the previous one was created and throws a helpful
exception.
> SparkContext constructor should throw exception if another SparkContext is
> already running
> ------------------------------------------------------------------------------------------
>
> Key: SPARK-4180
> URL: https://issues.apache.org/jira/browse/SPARK-4180
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Reporter: Josh Rosen
> Priority: Blocker
>
> Spark does not currently support multiple concurrently-running SparkContexts
> in the same JVM (see SPARK-2243). Therefore, SparkContext's constructor
> should throw an exception if there is an active SparkContext that has not
> been shut down via {{stop()}}.
> PySpark already does this, but the Scala SparkContext should do the same
> thing. The current behavior with multiple active contexts is unspecified /
> not understood and it may be the source of confusing errors (see the user
> error report in SPARK-4080, for example).
> This should be pretty easy to add: just add a {{activeSparkContext}} field to
> the SparkContext companion object and {{synchronize}} on it in the
> constructor and {{stop()}} methods; see PySpark's {{context.py}} file for an
> example of this approach.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
