At-least-once-guarantee semantics for all the data streamed into Ignite

[ght230 <gh...@163.com>]

I have read from the document about that "Data streamers are built in a
scalable and fault-tolerant fashion and provide at-least-once-guarantee
semantics for all the data streamed into Ignite." 

Can anyone tell me the more detailed theory about it and in what conditions
data streamers will put more than once data streamed into Ignite?



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/At-least-once-guarantee-semantics-for-all-the-data-streamed-into-Ignite-tp4991.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: At-least-once-guarantee semantics for all the data streamed into Ignite

[vkulichenko <va...@gmail.com>]

Hi,

It only means that if the processing of a streamed tuple fails (e.g., the
node fails in the middle of StreamReceiver execution), this tuple will be
remapped to a different node, so IgniteDataStreamer guarantees that it will
be processed.

Makes sense?

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/At-least-once-guarantee-semantics-for-all-the-data-streamed-into-Ignite-tp4991p5014.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.