Basically what happens is that whatever you set to the spec.taskManager.resource.memory will be set in the config as process memory. In Flink kubernetes the process is the pod so pod memory is always equal to process memory.
So basically the spec is a config shorthand, there is no reason to override it as you won't get a different behaviour at the end of the day. Gyula On Wed, Jun 14, 2023 at 11:55 AM Robin Cassan via user < user@flink.apache.org> wrote: > Hello all! > > I am using the flink kubernetes operator and I would like to set the value > for `taskmanager.memory.process.size`. I set the desired value in the > flinkdeployment resource specs (here, I want 55gb), however it looks like > the value that is effectively passed to the taskmanager is the same as the > pod memory setting (which is set to 59gb). > > For example, this flinkdeployment configuration: > ``` > Spec: > Flink Configuration: > taskmanager.memory.process.size: 55gb > Task Manager: > Resource: > Cpu: 6 > Memory: 59Gb > ``` > will create a pod with 59Gb total memory (as expected) but will also give > 59Gb to the memory.process.size instead of 55Gb, as seen in this TM log: > `Loading configuration property: taskmanager.memory.process.size, 59Gb` > > Maybe this part of the flink k8s operator code is responsible: > > https://github.com/apache/flink-kubernetes-operator/blob/d43e1ca9050e83b492b2e16b0220afdba4ffa646/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/config/FlinkConfigBuilder.java#L393 > > If so, I wonder what is the rationale for forcing the flink process memory > to be the same as the pod memory? > Is there a way to bypass that, for example by setting the desired > process.memory configuration differently? > > Thanks! >
