I think there is some misunderstanding here: a checkpoint IS (a snapshot of) the keyed state and operator state (among a few more things). [1]
[1] https://ci.apache.org/projects/flink/flink-docs-release-1.11/learn-flink/fault_tolerance.html#definitions On Wed, Oct 7, 2020 at 6:51 AM 大森林 <appleyu...@foxmail.com> wrote: > when the job is killed,state is also misssing. > so why we need keyed state?Is keyed state useful when we try to resuming > the killed job? > > > ------------------ 原始邮件 ------------------ > *发件人:* "Shengkai Fang" <fskm...@gmail.com>; > *发送时间:* 2020年10月7日(星期三) 中午12:43 > *收件人:* "大森林"<appleyu...@foxmail.com>; > *抄送:* "user"<user@flink.apache.org>; > *主题:* Re: why we need keyed state and operate state when we already have > checkpoint? > > The checkpoint is a snapshot for the job and we can resume the job if the > job is killed unexpectedly. The state is another thing to memorize the > intermediate result of calculation. I don't think the checkpoint can > replace state. > > 大森林 <appleyu...@foxmail.com> 于2020年10月7日周三 下午12:26写道： > >> Could you tell me: >> >> why we need keyed state and operator state when we already have >> checkpoint? >> >> when a running jar crash,we can resume from the checkpoint >> automatically/manually. >> So why did we still need keyed state and operator state. >> >> Thanks >> > -- Arvid Heise | Senior Java Developer <https://www.ververica.com/> Follow us @VervericaData -- Join Flink Forward <https://flink-forward.org/> - The Apache Flink Conference Stream Processing | Event Driven | Real Time -- Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany -- Ververica GmbH Registered at Amtsgericht Charlottenburg: HRB 158244 B Managing Directors: Timothy Alexander Steinert, Yip Park Tung Jason, Ji (Toni) Cheng
