You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Yikun Jiang (Jira)" <ji...@apache.org> on 2022/03/10 01:38:00 UTC

[jira] [Resolved] (SPARK-36060) Support backing off dynamic allocation increases if resources are "stuck"

     [ https://issues.apache.org/jira/browse/SPARK-36060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yikun Jiang resolved SPARK-36060.
---------------------------------
    Resolution: Fixed

Now minRes and queue supported have been supported by https://issues.apache.org/jira/browse/SPARK-38455

See also: 

minRes: https://issues.apache.org/jira/browse/SPARK-38187

queue: https://issues.apache.org/jira/browse/SPARK-38188

> Support backing off dynamic allocation increases if resources are "stuck"
> -------------------------------------------------------------------------
>
>                 Key: SPARK-36060
>                 URL: https://issues.apache.org/jira/browse/SPARK-36060
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Kubernetes
>    Affects Versions: 3.2.0
>            Reporter: Holden Karau
>            Priority: Major
>
> In a over-subscribed environment we may enter a situation where our requests for more pods are not going to be fulfilled. Adding more requests for more pods is not going to help and may slow down the scheduler. We should detect this situation and hold off on increasing pod requests until the scheduler allocates more pods to us. We have a limited version of this in the Kube scheduler it's self but it would be better to plumb this all the way through to the DA logic.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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