Hi Ashish, have you tried using Flink's RocksDBStateBackend? If your job accumulates state exceeding the available main memory, then you have to use a state backend which can spill to disk. The RocksDBStateBackend offers you exactly this functionality.
Cheers, Till On Mon, Apr 30, 2018 at 3:54 PM, ashish pok <ashish...@yahoo.com> wrote: > All, > > I am using noticing heap utilization creeping up slowly in couple of apps > which eventually lead to OOM issue. Apps only have 1 process function that > cache state. I did make sure I have a clear method invoked when events are > collected normally, on exception and on timeout. > > Are any other best practices others follow for memory backed states? > > Thanks, > > -- Ashish >
