[
https://issues.apache.org/jira/browse/SPARK-34334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon updated SPARK-34334:
---------------------------------
Fix Version/s: (was: 3.1.2)
3.1.1
> ExecutorPodsAllocator fails to identify some excess requests during
> downscaling
> -------------------------------------------------------------------------------
>
> Key: SPARK-34334
> URL: https://issues.apache.org/jira/browse/SPARK-34334
> Project: Spark
> Issue Type: Sub-task
> Components: Kubernetes
> Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.2.0, 3.1.1, 3.1.2
> Reporter: Attila Zsolt Piros
> Assignee: Attila Zsolt Piros
> Priority: Minor
> Fix For: 3.2.0, 3.1.1
>
>
> During downscaling there are two kinds of POD requests which can lead to POD
> deletion as it is identified as excess requests by the dynamic allocation:
> * timed out newly created POD requests (which even haven't reached the Pod
> Pending state, yet)
> * timed out pending pod requests
> The current implementation fails to delete a timed out pending pod requests
> when there are not enough timed out newly created POD requests to delete but
> there are some non-timed out ones.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
