Hi narashima, not sure whether this fits your use case, but have you considered creating a savepoint and analyzing it using the State Processor API [1]?
Best, Matthias [1] https://ci.apache.org/projects/flink/flink-docs-stable/dev/libs/state_processor_api.html#state-processor-api On Wed, Feb 10, 2021 at 6:08 PM narasimha <swamy.haj...@gmail.com> wrote: > It is not solving the problem. > > I could see the memory keep increasing, resulting in a lot of high GCs. > > There could be a memory leak, just want to know how to know if older keps > are skill alive, even after the pattern has been satisfied or within range > of the pattern has expired. > > Can someone suggest how to proceed further. >
