You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Holden Karau (Jira)" <ji...@apache.org> on 2021/07/23 23:27:00 UTC
[jira] [Resolved] (SPARK-35956) Support auto-assigning labels to
less important pods (e.g. decommissioning pods)
[ https://issues.apache.org/jira/browse/SPARK-35956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Holden Karau resolved SPARK-35956.
----------------------------------
Fix Version/s: 3.3.0
Target Version/s: 3.3.0
Resolution: Fixed
> Support auto-assigning labels to less important pods (e.g. decommissioning pods)
> --------------------------------------------------------------------------------
>
> Key: SPARK-35956
> URL: https://issues.apache.org/jira/browse/SPARK-35956
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes
> Affects Versions: 3.2.0
> Reporter: Holden Karau
> Assignee: Holden Karau
> Priority: Major
> Fix For: 3.3.0
>
>
> To allow for folks to use pod disruption budgets or replicasets we should indicate which pods Spark cares about "the least", those would be pods that are otherwise exiting soon.
>
> With PDBs the user would create a PDB representing the label of decommissioning executors and this could have a higher number of unavailable than the PDB for the "regular" execs. For people using replicasets in 1.21 we could also set a label of "controller.kubernetes.io/pod-deletion-cost" (see [https://github.com/kubernetes/kubernetes/pull/99163] ) to hint to the controller that a pod is less important to us.
--
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