Hey Karl, sorry for the late reply!
Let me first quickly answer your questions: > > - are expired session windows automatically removed from state? if > not, what's the best way to do it? > > Yes, they should get removed automatically. > > - > - how can we query state size? > > You can monitor the state size in the Flink web ui (there's a "Checkpointing" tab for each job) Or through Flink's metrics system: https://ci.apache.org/projects/flink/flink-docs-master/monitoring/metrics.html#checkpointing > > - > - how can we query number of windows in state? > > The window operator does not expose any metrics. I also have some questions :) - Have you considered using the RocksDB statebackend to mitigate the out of memory issues? - Why are you disabling the operator chaining? - Did you validate that the "TimeZone.setDefault(...)" setting ends up at the worker JVMs executing your code? (I suspect that you are only setting the TimeZone in the JVM executing the main() method) Best, Robert On Tue, Mar 3, 2020 at 7:23 PM karl.pullicino < karl.pullic...@gamesysgroup.com> wrote: > Added flink_oom_exception.txt > < > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/file/t2426/flink_oom_exception.txt> > > as originally forgot to attach it > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >
