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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.7, 3.0.2, 3.1.1
• Fix Version/s: 3.2.0
• Component/s: Shuffle, Spark Core
• Assignee: Kent Yao 2
• Reporter: Kent Yao 2
• Created: 29/Mar/21 06:15
• Updated: 30/Mar/21 02:03
• Resolved: 30/Mar/21 01:59

Description

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`

Issue Links

• links to: [Github] Pull Request #31990 (yaooqinn)