Hi all,

we are starting a lot of Flink jobs (streaming), and after we have started
200 or more jobs we see that the non-heap memory in the taskmanagers
increases a lot, to the point of killing the instances. We found out that
every time we start a new job, the committed non-heap memory increases by 5
to 10MB. Is this an expected behavior? Are there ways to prevent this?

Reply via email to