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

Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/12/05 23:51:00 UTC

[jira] [Updated] (SPARK-54619) Add sanity check for runner conf

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

ASF GitHub Bot updated SPARK-54619:
-----------------------------------
    Labels: pull-request-available  (was: )

> Add sanity check for runner conf
> --------------------------------
>
>                 Key: SPARK-54619
>                 URL: https://issues.apache.org/jira/browse/SPARK-54619
>             Project: Spark
>          Issue Type: Sub-task
>          Components: PySpark
>    Affects Versions: 4.2.0
>            Reporter: Tian Gao
>            Priority: Minor
>              Labels: pull-request-available
>
> Having some sanity checks on worker side is helpful to avoid deadlock caused by invalid message. For example if the message is malformed, the worker could wait for an unreasonable amount of data - if we are unlucky, there won't be any errors.
> Checking number of configurations is safe, effective and fast - we should do that.



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