Cc: Till Rohrmann , "user@flink.apache.org"
Subject: Re: Tumbling windows - increasing checkpoint size over time
Hi,
1. I am not the expert of Rocksdb. However, I think the state garbage
collection depends on the rocksdb compaction especially if the checkpoint
interval is 2s. This i
ann
> *Date: *Thursday, May 28, 2020 at 10:48 AM
> *To: *"Wissman, Matt"
> *Cc: *Guowei Ma , "user@flink.apache.org" <
> user@flink.apache.org>
> *Subject: *Re: Tumbling windows - increasing checkpoint size over time
>
>
>
> Hi Matt,
>
>
&g
link.apache.org"
Subject: Re: Tumbling windows - increasing checkpoint size over time
Hi Matt,
when using tumbling windows, then the checkpoint size is not only dependent on
the number of keys (which is equivalent to the number of open windows) but also
on how many events arrive for each
gt;
>
> Thanks!
>
>
>
> -Matt
>
>
>
>
>
> *From: *Till Rohrmann
> *Date: *Wednesday, May 27, 2020 at 9:00 AM
> *To: *Guowei Ma
> *Cc: *"Wissman, Matt" , "user@flink.apache.org" <
> user@flink.apache.org>
> *Subject: *Re:
-Matt
From: Till Rohrmann
Date: Wednesday, May 27, 2020 at 9:00 AM
To: Guowei Ma
Cc: "Wissman, Matt" , "user@flink.apache.org"
Subject: Re: Tumbling windows - increasing checkpoint size over time
LEARN FAST: This email originated outside of HERE.
Please do not click on li
Hi Matt,
could you give us a bit more information about the windows you are using?
They are tumbling windows. What's the size of the windows? Do you allow
lateness of events? What's your checkpoint interval?
Are you using event time? If yes, how is the watermark generated?
You said that the
Hi, Matt
The total size of the state of the window operator is related to the
number of windows. For example if you use keyby+tumblingwindow there
would be keys number of windows.
Hope this helps.
Best,
Guowei
Wissman, Matt 于2020年5月27日周三 上午3:35写道：
>
> Hello Flink Community,
>
>
>
> I’m running a
