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

Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2022/01/18 06:09:00 UTC

[jira] [Assigned] (FLINK-15648) Support to configure limit for CPU and memory requirement

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

Yang Wang reassigned FLINK-15648:
---------------------------------

    Assignee: Denis Nutiu

> Support to configure limit for CPU and memory requirement
> ---------------------------------------------------------
>
>                 Key: FLINK-15648
>                 URL: https://issues.apache.org/jira/browse/FLINK-15648
>             Project: Flink
>          Issue Type: New Feature
>          Components: Deployment / Kubernetes
>            Reporter: Canbin Zheng
>            Assignee: Denis Nutiu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, the native Kubernetes mode could support same request and limit for the cpu and memory resources. It will be a good improvement to allow different resource requests and limits. And it is very useful especially for the CPU resource since it heavily depends on the upstream workloads. 
>  
> For the implementation, we could have the four config options of limit-factor, which could make the JM/TM benefit from burst resources.
> {code:java}
> kubernetes.jobmanager.cpu.limit-factor 
> kubernetes.jobmanager.memory.limit-factor
> kubernetes.taskmanager.cpu.limit-factor
> kubernetes.taskmanager.memory.limit-factor{code}
>  



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