You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/03/16 22:54:08 UTC
[jira] [Updated] (SPARK-30055) Allow configurable restart policy of
driver and executor pods
[ https://issues.apache.org/jira/browse/SPARK-30055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-30055:
----------------------------------
Affects Version/s: (was: 3.0.0)
3.1.0
> Allow configurable restart policy of driver and executor pods
> -------------------------------------------------------------
>
> Key: SPARK-30055
> URL: https://issues.apache.org/jira/browse/SPARK-30055
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes
> Affects Versions: 3.1.0
> Reporter: Kevin Hogeland
> Priority: Major
>
> The current Kubernetes scheduler hard-codes the restart policy for all pods to be "Never". To restart a failed application, all pods have to be deleted and rescheduled, which is very slow and clears any caches the processes may have built. Spark should allow a configurable restart policy for both drivers and executors for immediate restart of crashed/killed drivers/executors as long as the pods are not evicted. (This is not about eviction resilience, that's described in this issue: SPARK-23980)
> Also, as far as I can tell, there's no reason the executors should be set to never restart. Should that be configurable or should it just be changed to Always?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org