SO too:
https://stackoverflow.com/questions/70986020/flink-job-requiring-a-lot-of-memory-despite-using-rocksdb-state-backend
ally, the images I am using have
`jemalloc` in place for memory allocation, which should avoid memory
fragmentation issues observed with malloc in the past.
PS: I posted the issue in SO too:
https://stackoverflow.com/questions/70986020/flink-job-requiring-a-lot-of-memory-despite-using-rocksdb-state-backend
t; Is there an effective way of limiting the memory that rocksdb takes
> > (to that available on the running pods)? Nothing I have found/tried
> > out so far has worked. Theoretically, the images I am using have
> > `jemalloc` in place for memory allocation, which should avoid memory
> > fragmentation issues observed with malloc in the past.
> >
> > PS: I posted the issue in SO too:
> >
https://stackoverflow.com/questions/70986020/flink-job-requiring-a-lot-of-memory-despite-using-rocksdb-state-backend
>
>
>
