[jira] [Resolved] (SPARK-34894) Use 'io.connectionTimeout' as a hint instead of `spark.network.timeout`

["Kent Yao (Jira)" <ji...@apache.org>]

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

Kent Yao resolved SPARK-34894.
------------------------------
    Fix Version/s: 3.2.0
       Resolution: Fixed

Issue resolved by pull request 31990
[https://github.com/apache/spark/pull/31990]

> Use 'io.connectionTimeout' as a hint instead of `spark.network.timeout`
> -----------------------------------------------------------------------
>
>                 Key: SPARK-34894
>                 URL: https://issues.apache.org/jira/browse/SPARK-34894
>             Project: Spark
>          Issue Type: Improvement
>          Components: Shuffle, Spark Core
>    Affects Versions: 2.4.7, 3.0.2, 3.1.1
>            Reporter: Kent Yao
>            Priority: Major
>             Fix For: 3.2.0
>
>
> Currently, when a connection for TransportClient is marked as idled and closed, we suggest users adjust `spark.network.timeout` for all transport modules. As a lot of timeout configs will fallback to the `spark.network.timeout`, this could be a piece of overkill advice, we should give a more targeted one with `spark.${moduleName}.io.connectionTimeout`



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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