[ https://issues.apache.org/jira/browse/FLINK-24093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-24093: ----------------------------------- Labels: pull-request-available stale-minor (was: pull-request-available) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Supports setting the percentage of kubernetes Request resources > --------------------------------------------------------------- > > Key: FLINK-24093 > URL: https://issues.apache.org/jira/browse/FLINK-24093 > Project: Flink > Issue Type: Improvement > Components: Deployment / Kubernetes > Reporter: liuzhuo > Priority: Minor > Labels: pull-request-available, stale-minor > > For the current native Kubernetes, we start the job to apply for resources > (CPU,Memory) of the same *limit* and *request*, so as to achieve the best > performance. However, in general, when the kubernetes cluster resources are > used up by request allocation, In fact, there are still some physical > resources left. If there is a way to reduce the number of requests per job, > more jobs can be run and the resource utilization of the cluster can be > improved. > Here are some simple configurations to scale down the value of request: > > {code:java} > kubernetes.cpu.request.percent > kubernetes.mem.request.percent > {code} > > *kubernetes.mem.request.percent*: the default value is 1.0, the effective > range of 0.0 to 1.0, the meaning of this value is: If the value is 0.5 and > the total memory of taskmanager/jobmanager is 2048MB, the value of request is > 2048MB*0.5=1024MB. That is, if the remaining memory of nodes is larger than > 1024MB, pods can be allocated to run > *kubernetes.cpu.request.percent:*the default value is 1.0, the effective > range of 0.0 to 1.0, the meaning of this value is: If the value is 0.5 and > the number of cpus requested by TaskManager/JobManager is 1, the value of > request is 1 x 0.5=0.5, that is, the remaining CPU usage of Nodes is greater > than 0.5 to allocate pods to run -- This message was sent by Atlassian Jira (v8.20.1#820001)