spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Or (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SPARK-6133) SparkContext#stop is not idempotent
Date Tue, 03 Mar 2015 23:11:06 GMT

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

Andrew Or updated SPARK-6133:
-----------------------------
    Target Version/s: 1.2.2, 1.4.0  (was: 1.4.0)

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


Mime
View raw message