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/12/31 04:18:49 UTC
[jira] [Commented] (SPARK-6166) Add config to limit number of
concurrent outbound connections for shuffle fetch
[ https://issues.apache.org/jira/browse/SPARK-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075678#comment-15075678 ]
Reynold Xin commented on SPARK-6166:
------------------------------------
[~zsxwing] can you pick this one up?
> Add config to limit number of concurrent outbound connections for shuffle fetch
> -------------------------------------------------------------------------------
>
> Key: SPARK-6166
> URL: https://issues.apache.org/jira/browse/SPARK-6166
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 1.4.0
> Reporter: Mridul Muralidharan
> Priority: Minor
>
> spark.reducer.maxMbInFlight puts a bound on the in flight data in terms of size.
> But this is not always sufficient : when the number of hosts in the cluster increase, this can lead to very large number of in-bound connections to one more nodes - causing workers to fail under the load.
> I propose we also add a spark.reducer.maxReqsInFlight - which puts a bound on number of outstanding outbound connections.
> This might still cause hotspots in the cluster, but in our tests this has significantly reduced the occurance of worker failures.
--
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