There are two things that you may want to try:
- Configure 'state.backend.rocksdb.memory.managed' to true. That tells
RocksDBStateBackend to try to limit its memory consumption within the
managed memory size.
- Increase JVM Overhead Memory Size (via
'taskmanager.memory.jvm-overhead.[min|max|fractio
Hi Xintong,
Thanks very much for the response. Let me check out the new UI on flink
1.12.
The reason I asked this question is because our flink cluster on k8s shows
a container_working_set_bytes(used by OOMkiller) to be > 3Gb. I assume that
the used(heap, non-heap) values on the UI are correct. If
Hi Sudharsan,
The non-heap max is decided by JVM automatically and is not controlled by
Flink. Moreover, it doesn't mean Flink will use up to that size of non-heap
memory.
These metrics are fetched directly from JVM and do not correspond well with
Flink's memory configurations, which very often l
