You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2014/11/06 18:39:35 UTC

[jira] [Commented] (SPARK-4188) Shuffle fetches should be retried at a lower level

    [ https://issues.apache.org/jira/browse/SPARK-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200527#comment-14200527 ] 

Apache Spark commented on SPARK-4188:
-------------------------------------

User 'aarondav' has created a pull request for this issue:
https://github.com/apache/spark/pull/3101

> Shuffle fetches should be retried at a lower level
> --------------------------------------------------
>
>                 Key: SPARK-4188
>                 URL: https://issues.apache.org/jira/browse/SPARK-4188
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.2.0
>            Reporter: Aaron Davidson
>
> During periods of high network (or GC) load, it is not uncommon that IOExceptions crop up around connection failures when fetching shuffle files. Unfortunately, when such a failure occurs, it is interpreted as an inability to fetch the files, which causes us to mark the executor as lost and recompute all of its shuffle outputs.
> We should allow retrying at the network level in the event of an IOException in order to avoid this circumstance.



--
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