You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/03/13 19:34:38 UTC

[jira] [Resolved] (SPARK-6133) SparkContext#stop is not idempotent

     [ https://issues.apache.org/jira/browse/SPARK-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-6133.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.1

> SparkContext#stop is not idempotent
> -----------------------------------
>
>                 Key: SPARK-6133
>                 URL: https://issues.apache.org/jira/browse/SPARK-6133
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.0.0
>            Reporter: Andrew Or
>            Assignee: Andrew Or
>             Fix For: 1.2.2, 1.4.0, 1.3.1
>
>
> If we call sc.stop() twice, the listener bus will attempt to log an event after stop() is called, resulting in a scary error message. This happens if Spark calls sc.stop() internally (it does this on certain error conditions) and the application code calls it again, for instance.



--
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