[
https://issues.apache.org/jira/browse/SPARK-25515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625575#comment-16625575
]
Prashant Sharma commented on SPARK-25515:
-----------------------------------------
Also add a fail fast option, if the pod creation fails for configurable x
number of times, then fail with pods not deleted.
> Add a config property for disabling auto deletion of PODS for debugging.
> ------------------------------------------------------------------------
>
> Key: SPARK-25515
> URL: https://issues.apache.org/jira/browse/SPARK-25515
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes
> Affects Versions: 2.5.0
> Reporter: Prashant Sharma
> Priority: Major
>
> Currently, if a pod fails to start due to some failure, it gets removed and
> new one is attempted. These sequence of events go on, until the app is
> killed. Given the speed of creation and deletion, it becomes difficult to
> debug the reason for failure.
> So adding a configuration parameter to disable auto-deletion of pods, will be
> helpful for debugging.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
