You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Shixiong Zhu (JIRA)" <ji...@apache.org> on 2016/02/12 07:45:18 UTC
[jira] [Commented] (SPARK-6166) Limit number of in flight outbound
requests for shuffle fetch
[ https://issues.apache.org/jira/browse/SPARK-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144148#comment-15144148 ]
Shixiong Zhu commented on SPARK-6166:
-------------------------------------
Sure. Done
> Limit number of in flight outbound requests 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
> Fix For: 2.0.0
>
>
> 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 requests.
> 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