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

Apache Spark commented on SPARK-30821:
--------------------------------------

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

> Executor pods with multiple containers will not be rescheduled unless all 
> containers fail
> -----------------------------------------------------------------------------------------
>
>                 Key: SPARK-30821
>                 URL: https://issues.apache.org/jira/browse/SPARK-30821
>             Project: Spark
>          Issue Type: Improvement
>          Components: Kubernetes, Spark Core
>    Affects Versions: 3.1.0
>            Reporter: Kevin Hogeland
>            Assignee: Apache Spark
>            Priority: Major
>
> Since the restart policy of launched pods is Never, additional handling is 
> required for pods that may have sidecar containers. The executor should be 
> considered failed if any containers have terminated and have a non-zero exit 
> code, but Spark currently only checks the pod phase. The pod phase will 
> remain "running" as long as _any_ pods are still running. Kubernetes sidecar 
> support in 1.18/1.19 does not address this situation, as sidecar containers 
> are excluded from pod phase calculation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to