You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/02/18 11:04:18 UTC

[jira] [Updated] (SPARK-13369) Number of consecutive fetch failures for a stage before the job is aborted should be configurable

     [ https://issues.apache.org/jira/browse/SPARK-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen updated SPARK-13369:
------------------------------
    Priority: Minor  (was: Major)

While I can appreciate that, is there any value that would work for indefinitely long-running jobs? This is really only an issue for streaming; non-streaming jobs are not intended to run a long time. Does it come up in streaming?

>  Number of consecutive fetch failures for a stage before the job is aborted should be configurable
> --------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-13369
>                 URL: https://issues.apache.org/jira/browse/SPARK-13369
>             Project: Spark
>          Issue Type: Improvement
>    Affects Versions: 1.6.0
>            Reporter: Sital Kedia
>            Priority: Minor
>
> Currently it is hardcode inside code. We need to make it configurable because for long running jobs, the chances of fetch failures due to machine reboot is high and we need a configuration parameter to bump up that number. 



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