xintongsong opened a new pull request #11110: [FLINK-16111][k8s] Fix Kubernetes 
deployment not respecting 'taskmanager.cpu.cores'.
URL: https://github.com/apache/flink/pull/11110
 
 
   ## What is the purpose of the change
   
   This PR fix that Kubernetes deployment not respecting 'taskmanager.cpu.core'.
   The expected behavior for cpu configuration is to fallback the cpu 
configuration with the following order:
   1. common cpu config option ('taskmanager.cpu.core')
   2. K8s/Yarn/Mesos config option ('kubernetes.taskmanager.cpu' for Kubernetes)
   3. number of slots ('taskmanager.numberOfTaskSlots')
   
   ## Brief change log
   
   - a43e139a4ffeeb06b00db4163e329dfcbfbb9f3b: Make Kubernetes to respect 
'taskmanager.cpu.cores'.
   - 9db123635d9b3142f3bf9b1b61347f7d46ca4890, 
c330e78bc64b398d2ff483ab3f996db3958ec2fd: Hotfixes for adding test cases 
validating the same behavior on Yarn/Mesos deployments.
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   - Add test cases in `KubernetesResourceManagerTest`
   - Add test cases in `YarnResourceManagerTest`
   - Update existing test cases in `MesosTaskManagerParametersTest`
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to