You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2022/07/29 22:10:00 UTC
[jira] [Commented] (SPARK-39919) Hitting Interrupt when no cell is running kills pyspark jupyter kernel
[ https://issues.apache.org/jira/browse/SPARK-39919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573175#comment-17573175 ]
Dongjoon Hyun commented on SPARK-39919:
---------------------------------------
Thank you for reporting, [~nsingl00] . I'll take a look at this issue in the community.
> Hitting Interrupt when no cell is running kills pyspark jupyter kernel
> ----------------------------------------------------------------------
>
> Key: SPARK-39919
> URL: https://issues.apache.org/jira/browse/SPARK-39919
> Project: Spark
> Issue Type: Bug
> Components: PySpark
> Affects Versions: 3.2.2
> Reporter: Neha Singla
> Priority: Blocker
>
> In Pyspark 3.2 kernel with Jupyter notebook, When no cell is running and I hit interrupt kernel, it actually kills pyspark kernel, where it's supposed to do NOTHING.|
> I defined one startup script and in that startup script, If I override default interrupt signal handler to SIGIGN, it works.
> {quote} signal(SIGINT, SIG_IGN)
> {quote}
> Are users of pyspark need to do this step explicity? I wonder why it doesn't work by default
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org