Hi,
for most windows, all state is cleared through FIRE_AND_PURGE, except for
windows that are subtypes of merging windows, such as session windows. Here,
the state still remembers the window itself until the watermark passes the
session timeout+allowed lateness. This is done so that elements
One more attempt to get some feedback on this. It basically boils down to using
High-Level Window API in scenarios where keys are unbounded / infinite but can
be expired after certain time. From what we have observed (solution 2 below),
some properties of keys are still in state (guessing key
All,
I have been doing a little digging on this and to Stefan's point incrementing
memory (not necessarily leak) was essentially because of keys that were
incrementing as I was using time buckets concatenated with actual key to make
unique sessions.
Taking a couple of steps back, use case is
Stefan, All,
If there are no further thoughts on this I am going to switch my app to low
level Process API. I still think there is an easier solution here which I am
missing but I will revisit that after I fix Production issue.
Thanks, Ashish
Sent from Yahoo Mail for iPhone
On Thursday,
Hi,
it is possible that the number of processing time timers can grow, because
internal timers are scoped by time, key, and namespace (typically this means
„window“, because each key can be part of multiple windows). So if the number
of keys in your application is steadily growing this can
Right, thats where I am headed now but was wondering there are any “gochas” I
am missing before I try and dig into a few gigs of heap dump.
Thanks, Ashish
Sent from Yahoo Mail for iPhone
On Monday, June 18, 2018, 3:37 AM, Stefan Richter
wrote:
Hi,
can you take a heap dump from a JVM that
Hi,
can you take a heap dump from a JVM that runs into the problem and share it
with us? That would make finding the cause a lot easier.
Best,
Stefan
> Am 15.06.2018 um 23:01 schrieb ashish pok :
>
> All,
>
> I have another slow Memory Leak situation using basic TimeSession Window
>
All,
I have another slow Memory Leak situation using basic TimeSession Window
(earlier it was GlobalWindow related that Fabian helped clarify).
I have a very simple data pipeline:
DataStream processedData = rawTuples
