THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- `jobmanager.heap.size` option is deluding for the containerised environments (Yarn/Mesos/Kubernetes) because it does not represent the JM’s JVM heap size but the total process memory consumed by the Flink JVM process including container cut-off. It is used to set the JM container memory size requested in a containerised environment.
- The purpose of the container cut-off can be also confusing on its own, the main use cases for it are:
- Direct memory usage by Flink or user code dependencies (there are certain cases where user code is run during the job start up)
- JVM Metaspace
- Other JVM overhead
...