Hi Till, We did some investigation and found this memory usage point to rocksdbstatebackend running on managed memory. So far we have seen this bug in rocksdbstatebackend on managed memory. we followed suggestion [1] and disabled managed memory management so far not seeing issue.
I felt this might be a major bug since we run flink 1.11.2 with managed RocksDBstatebackend in mulitple large production jobs and consistency repo yarn kill after job runs a period of time. [1] http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Debugging-quot-Container-is-running-beyond-physical-memory-limits-quot-on-YARN-for-a-long-running-stb-td38227.html -- Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
