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

Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2023/10/31 22:34:00 UTC

[jira] [Assigned] (SPARK-45739) Catch IOException instead of EOFException alone for faulthandler

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

Hyukjin Kwon reassigned SPARK-45739:
------------------------------------

    Assignee: Hyukjin Kwon

> Catch IOException instead of EOFException alone for faulthandler
> ----------------------------------------------------------------
>
>                 Key: SPARK-45739
>                 URL: https://issues.apache.org/jira/browse/SPARK-45739
>             Project: Spark
>          Issue Type: Improvement
>          Components: PySpark
>    Affects Versions: 4.0.0
>            Reporter: Hyukjin Kwon
>            Assignee: Hyukjin Kwon
>            Priority: Major
>              Labels: pull-request-available
>
> {{spark.python.worker.faulthandler.enabled}} can describe the fatal exception such as segfault hanlder. Exceptions such as {{java.net.SocketException: Connection reset}} can happen because the worker unexpectedly die. We should better catch all IO exception there.



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