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

Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2021/12/06 05:47:00 UTC

[jira] [Assigned] (SPARK-37004) Job cancellation causes py4j errors on Jupyter due to pinned thread mode

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

Apache Spark reassigned SPARK-37004:
------------------------------------

    Assignee:     (was: Apache Spark)

> Job cancellation causes py4j errors on Jupyter due to pinned thread mode
> ------------------------------------------------------------------------
>
>                 Key: SPARK-37004
>                 URL: https://issues.apache.org/jira/browse/SPARK-37004
>             Project: Spark
>          Issue Type: Bug
>          Components: PySpark
>    Affects Versions: 3.2.0
>            Reporter: Xiangrui Meng
>            Priority: Blocker
>         Attachments: pinned.ipynb
>
>
> Spark 3.2.0 turned on py4j pinned thread mode by default (SPARK-35303). However, in a jupyter notebook, after I cancel (interrupt) a long-running Spark job, the next Spark command will fail with some py4j errors. See attached notebook for repro.
> Cannot reproduce the issue after I turn off pinned thread mode .



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org