You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2014/06/12 19:09:04 UTC

[jira] [Updated] (SPARK-1740) Pyspark cancellation kills unrelated pyspark workers

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

Thomas Graves updated SPARK-1740:
---------------------------------

    Priority: Critical  (was: Major)

> Pyspark cancellation kills unrelated pyspark workers
> ----------------------------------------------------
>
>                 Key: SPARK-1740
>                 URL: https://issues.apache.org/jira/browse/SPARK-1740
>             Project: Spark
>          Issue Type: Bug
>          Components: PySpark
>    Affects Versions: 1.0.0
>            Reporter: Aaron Davidson
>            Priority: Critical
>
> PySpark cancellation calls SparkEnv#destroyPythonWorker. Since there is one python worker per process, this would seem like a sensible thing to do. Unfortunately, this method actually destroys a python daemon, and all associated workers, which generally means that we can cause failures in unrelated Pyspark jobs.
> The severity of this bug is limited by the fact that the Pyspark daemon is easily recreated, so the tasks will succeed after being restarted.



--
This message was sent by Atlassian JIRA
(v6.2#6252)