Thanks again, maybe the jvm overhead param will act as the margin I want,
I'll try that :)
Robin
Le mer. 14 juin 2023 à 15:28, Gyula Fóra a écrit :
> Again, this has absolutely nothing to do with the Kubernetes Operator, but
> simply how Flink Kubernetes Memory configs work:
>
> https://nightli
Again, this has absolutely nothing to do with the Kubernetes Operator, but
simply how Flink Kubernetes Memory configs work:
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/memory/mem_tuning/#configure-memory-for-containers
You can probably play around with: jobmanager.memory.
Thanks Gyula for your answer! I'm wondering about your claim:
> In Flink kubernetes the process is the pod so pod memory is always equal
to process memory
Why should the flink TM process use the whole container (and so, the whole
pod) memory?
Before migrating to the k8s operator, we still used Fli
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 overri
