You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Kent Yao (Jira)" <ji...@apache.org> on 2021/03/29 06:16:00 UTC

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

Kent Yao created SPARK-34894:
--------------------------------

             Summary: 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: 3.1.1, 3.0.2, 2.4.7
            Reporter: Kent Yao


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