dnutiu opened a new pull request #17098:
URL: https://github.com/apache/flink/pull/17098
## What is the purpose of the change
The purpose of this PR is to allow the user to configure the Taskmanager's
and Jobmanager's CPU limits when deploying Flink using the Kubernetes Resource
provider.
The "kubernetes.jobmanager.cpu.limit-factor" will calculate the CPU limit of
the Jobmanager using the following formula: jobmanager cpu * limit-factor. The
"kubernetes.taskmanager.cpu.limit-factor" will do the same for the Taskmanager.
## Brief change log
- Added the "kubernetes.jobmanager.cpu.limit-factor" config option to
configure the Jobmanager's limit CPU when using the Kubernetes resource
provider.
- Added the "kubernetes.taskmanager.cpu.limit-factor" config option to
configure the Taskmanager's limit CPU when using the Kubernetes resource
provider.
## Verifying this change
This change added tests and can be verified as follows:
- *Added getter tests in KubernetesJobManagerParametersTest.java and
KubernetesTaskManagerParametersTest.java.*
- *Ensured the resource CPU limits are set correctly for the Jobmanager by
modifying the InitJobManagerDecoratorTest.java test*
- *Ensured the resource CPU limits are set correctly for the Taskmanager
by modifying the InitTaskManagerDecoratorTest.java test*
## 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): don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: yes
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? yes
- If yes, how is the feature documented? JavaDocs
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
