[jira] [Resolved] (SPARK-16956) Make ApplicationState.MAX_NUM_RETRY configurable

["Josh Rosen (JIRA)" <ji...@apache.org>]

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

Josh Rosen resolved SPARK-16956.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0
                   2.0.1
                   1.6.3

Issue resolved by pull request 14544
[https://github.com/apache/spark/pull/14544]

> Make ApplicationState.MAX_NUM_RETRY configurable
> ------------------------------------------------
>
>                 Key: SPARK-16956
>                 URL: https://issues.apache.org/jira/browse/SPARK-16956
>             Project: Spark
>          Issue Type: New Feature
>          Components: Deploy
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>             Fix For: 1.6.3, 2.0.1, 2.1.0
>
>
> The {{ApplicationState.MAX_NUM_RETRY}} setting, which controls the maximum number of back-to-back executor failures that the standalone cluster manager will tolerate before removing a faulty application, is currently a hardcoded constant (10), but there are use-cases for making it configurable (TBD in my PR). We should add a new configuration key to let users customize this.



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