[FLINK-15648] Support to configure limit for CPU and memory requirement

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.15.0
• Component/s: Deployment / Kubernetes
• Labels: pull-request-available
• Assignee: Denis Nutiu
• Reporter: Canbin Zheng
• Created: 19/Jan/20 03:14
• Updated: 21/Jan/22 02:48
• Resolved: 21/Jan/22 02:48

Description

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.

kubernetes.jobmanager.cpu.limit-factor 
kubernetes.jobmanager.memory.limit-factor
kubernetes.taskmanager.cpu.limit-factor
kubernetes.taskmanager.memory.limit-factor

 

Issue Links

• duplicates: FLINK-25378 kubernetes's request/limit resource can been seperated?
• relates to: FLINK-24150 Support to configure cpu resource request and limit in pod template
• links to: GitHub Pull Request #17098