Hi Pranjul,
which deployment mode are you using?
- For session cluster, I'd say it's possible that memory grows with # of
jobs.
- For application mode, there is actual user-code executed, so if you're
using some native libraries in your job driver, that may be another reason
for the growing memor
Hi Pranjul,
First of all, you adopted on-heap state backend: HashMapStateBackend, which
would not use native off-heap memory. Moreover, JobManager would not initialize
any keyed state backend instance. And if not enable high availability,
JobManagerCheckpointStorage would also not use direct me
