[SPARK-44241] Set io.connectionTimeout/connectionCreationTimeout to zero or negative will cause executor incessantes cons/destructions

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.2, 3.4.1, 3.5.0
• Fix Version/s: 3.3.3, 3.4.2, 3.5.0
• Component/s: Spark Core
• Assignee: Kent Yao
• Reporter: Kent Yao
• Created: 29/Jun/23 08:03
• Updated: 23/Aug/23 00:41
• Resolved: 30/Jun/23 10:34

Description

2023-06-28 14:57:23 CST Bootstrap WARN - Failed to set channel option 'CONNECT_TIMEOUT_MILLIS' with value '-1000' for channel '[id: 0xf4b54a73]'
java.lang.IllegalArgumentException: connectTimeoutMillis : -1000 (expected: >= 0)
	at io.netty.util.internal.ObjectUtil.checkPositiveOrZero(ObjectUtil.java:144) ~[netty-common-4.1.74.Final.jar:4.1.74.Final] 

Issue Links

• causes: SPARK-44920 Use await() instead of awaitUninterruptibly() in TransportClientFactory.createClient()
• links to: [Github] Pull Request #41785 (yaooqinn)