Re: Implications of taskmanager.memory.process.size

2020-07-09 Thread Vishal Santoshi
Got it. That was what I always thought but needed to be sure. Thank you for confirming On Thu, Jul 9, 2020 at 9:39 PM Xintong Song wrote: > Hi Vishal, > > If you have streaming jobs only and do not use RocksDB, you can tune the > fraction (taskmanager.memory.managed.fraction) to 0. In this

Re: Implications of taskmanager.memory.process.size

2020-07-09 Thread Xintong Song
Hi Vishal, If you have streaming jobs only and do not use RocksDB, you can tune the fraction (taskmanager.memory.managed.fraction) to 0. In this way, no more off-heap managed memory will be reserved for the user code execution. Please be aware that this does not mean the JVM heap will get all of t

Re: Implications of taskmanager.memory.process.size

2020-07-09 Thread Vishal Santoshi
ager.memory.process.size(none)MemorySizeTotal Process Memory size for the TaskExecutors. This includes all the memory that a TaskExecutor consumes, consisting of Total Flink Memory, JVM Metaspace, and JVM Overhead. On containerized setups, this should be set to the container memory. See also 'taskm

Implications of taskmanager.memory.process.size

2020-07-09 Thread Vishal Santoshi
Hello folks, As established https://ci.apache.org/projects/flink/flink-docs-stable/ops/config.html#memory-configuration , I set the taskmanager.memory.process.size and taskmanager.memory.task.off-heap.size in my flink-conf.yaml and I see the 2 properties being pulled in. * - Load