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 2021/10/20 05:53:00 UTC
[jira] [Resolved] (SPARK-37049) executorIdleTimeout is not working
for pending pods on K8s
[ https://issues.apache.org/jira/browse/SPARK-37049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun resolved SPARK-37049.
-----------------------------------
Fix Version/s: 3.1.3
3.2.1
3.3.0
Resolution: Fixed
Issue resolved by pull request 34319
[https://github.com/apache/spark/pull/34319]
> executorIdleTimeout is not working for pending pods on K8s
> ----------------------------------------------------------
>
> Key: SPARK-37049
> URL: https://issues.apache.org/jira/browse/SPARK-37049
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes, Spark Core
> Affects Versions: 3.1.0
> Reporter: Weiwei Yang
> Assignee: wwei
> Priority: Major
> Fix For: 3.3.0, 3.2.1, 3.1.3
>
>
> SPARK-33099 added the support to respect "spark.dynamicAllocation.executorIdleTimeout" in ExecutorPodsAllocator. However, when it checks if a pending executor pod is timed out, it checks against the pod's "startTime". A pending pod "startTime" is empty, and this causes the function "isExecutorIdleTimedOut()" always return true for pending pods.
> This caused the issue, pending pods are deleted immediately when a stage is finished and several new pods got recreated again in the next stage.
--
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