Hello, We have been facing this oomkill issue, where task managers are getting restarted with this error. I am seeing memory consumption increasing in a linear manner, i have given memory and CPU as high as possible but still facing the same issue.
We are using rocksdb for the state backend, is there a way to find which operator causing this issue? or find which operator takes more memory? Any good practice that we can follow? We are using broadcast state. Thanks, Prashant
