Hi Alexey, thanks for reaching out to the Flink community. I'm not 100% sure whether you have an actual issue or whether it's just the changed behavior you are confused about. The change you're describing was introduced in Flink 1.12 as part of the work on FLIP-104 [1] exposing the actual memory usage through the web UI. Does this answer your question?
Best, Matthias [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-104%3A+Add+More+Metrics+to+Jobmanager On Sat, Jan 16, 2021 at 5:35 AM Alexey Trenikhun <[email protected]> wrote: > Hello, > I was trying to deploy Flink 1.12.0 Application cluster on k8s, I have > following job manager arguments: > *standalone-job --job-classname > com.x.App --job-id 00000000000000000000000000000000 @/opt/flink/conf/fsp.conf* > > However, when I print *args* from App.main(): > > [@/opt/flink/conf/ssp.conf, -D, > jobmanager.memory.off-heap.size=134217728b, -D, > jobmanager.memory.jvm-overhead.min=280552338b, -D, > *jobmanager.memory.jvm-metaspace.size=268435456b, > -D, jobmanager.memory.heap.size=2122317824b, -D, > jobmanager.memory.jvm-overhead.max=280552338b**]* > > Looks like > With Flink 1.11.3 same deployment worked as expected - the job was only > getting [@/opt/flink/conf/ssp.conf] > > Thanks, > Alexey >
