Hi Stephan - incremental checkpointing sounds really interesting and
useful, I look forward to trying it out.
Thanks,
Zach
On Wed, Apr 6, 2016 at 4:39 AM Stephan Ewen wrote:
> Hi Zach!
>
> I am working on incremental checkpointing, hope to have it in the master
> in the next weeks.
>
> The cur
Hi Zach!
I am working on incremental checkpointing, hope to have it in the master in
the next weeks.
The current approach is a to have a full self-contained checkpoint every
once in a while, and have incremental checkpoints most of the time. Having
a full checkpoint every now and then spares you
Thanks for the details Konstantin and Ufuk!
On Tue, Apr 5, 2016 at 2:39 PM Konstantin Knauf <
konstantin.kn...@tngtech.com> wrote:
> Hi Ufuk,
>
> I thought so, but I am not sure when and where ;) I will let you know,
> if I come across it again.
>
> Cheers,
>
> Konstantin
>
> On 05.04.2016 21:10
Hi Ufuk,
I thought so, but I am not sure when and where ;) I will let you know,
if I come across it again.
Cheers,
Konstantin
On 05.04.2016 21:10, Ufuk Celebi wrote:
> Hey Zach and Konstantin,
>
> Great questions and answers. We can try to make this more explicit in the
> docs.
>
> On Tue, A
Hey Zach and Konstantin,
Great questions and answers. We can try to make this more explicit in the docs.
On Tue, Apr 5, 2016 at 8:54 PM, Konstantin Knauf
wrote:
> To my knowledge flink takes care of deleting old checkpoints (I think it
> says so in the documentation about savepoints.). In my exp
Hi Zach,
some answers/comments inline.
Cheers
Konstantin
On 05.04.2016 20:39, Zach Cox wrote:
> Hi - I have some questions regarding Flink's checkpointing, specifically
> related to storing state in the backends.
>
> So let's say an operator in a streaming job is building up some state.
> When
