You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2015/01/05 19:39:34 UTC
[jira] [Resolved] (SPARK-4688) Have a single shared network timeout
in Spark
[ https://issues.apache.org/jira/browse/SPARK-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reynold Xin resolved SPARK-4688.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
> Have a single shared network timeout in Spark
> ---------------------------------------------
>
> Key: SPARK-4688
> URL: https://issues.apache.org/jira/browse/SPARK-4688
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Patrick Wendell
> Priority: Critical
> Fix For: 1.3.0
>
>
> We have several different timeouts, but in most cases users just want to set something that is large enough that they can avoid GC pauses. We should have a single conf "spark.network.timeout" that is used as the default timeout for all network interactions. This can replace the following timeouts:
> {code}
> spark.core.connection.ack.wait.timeout
> spark.akka.timeout
> spark.storage.blockManagerSlaveTimeoutMs (undocumented)
> spark.shuffle.io.connectionTimeout (undocumented)
> {code}
> Of course, for compatibility we should respect the old ones when they are set. This idea was proposed originally by [~rxin] and I'm paraphrasing his suggestion here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org