Hello, Generally speaking the designed solution will most probably combine upstream backup with asynchronous state checkpointing. We are looking into ways to minimise the communication and recovery costs by exploiting properties of the stream (eg. recomputable segments-windows). Are you also working on fault tolerance?
Paris On 11 Oct 2014, at 18:43, cY <[email protected]> wrote: > Thanks for reply > Is there any idea about it?This is such a challenge~ > I care this problem a lot. : ) > > > > > ------------------ 原始邮件 ------------------ > 发件人: "Gyula Fóra";<[email protected]>; > 发送时间: 2014年10月12日(星期天) 凌晨0:38 > 收件人: "dev"<[email protected]>; > > 主题: Re: a question about Exactly once processing > > > > Hey, > > There is currently an ongoing effort to enable stateful exactly once > processing guarantees in Flink Streaming, but there is no currently > available version that supports that. We expect this to be available in the > next release after 0.7 > > Regards, > Gyula > > On Sat, Oct 11, 2014 at 6:31 PM, cY <[email protected]> wrote: > >> And How to make exactly once processing : P >> >> >> ------------------ Original ------------------ >> From: "cY";<[email protected]>; >> Date: Sun, Oct 12, 2014 00:30 AM >> To: "dev"<[email protected]>; >> >> Subject: a question about Exactly once processing >> >> >> >> As we know, with acker storm can process data at least once. If we want it >> to process data exactly once, the status of stream must be >> saved.Trident(storm's DAG abstract) leaves this problem to users.I would >> like to know where flink save the status of stream >> : ) Thanks a lot
