Effect of Autoflush frequency in Ignite Data Streamer

[rishi007bansod <ri...@gmail.com>]

Suppose autoflush frequency is 10000msec for ignite data streamer that put
data into cache. Now if I query this cache, then will this query result also
include data from data streamer buffer(which is not flushed into
cache)?(whose flush frequency we have set to 10 sec) 



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Effect-of-Autoflush-frequency-in-Ignite-Data-Streamer-tp10977.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Effect of Autoflush frequency in Ignite Data Streamer

[Andrey Mashenkov <an...@gmail.com>]

Hi Rishi,

No, according to javadoc there is no such guarantee.
If you need guarantee method flush() should be used.

* Gets automatic flush frequency. Essentially, this is the time after which the
* streamer will make an attempt to submit all data added so far to remote nodes.
* Note that there is no guarantee that data will be delivered after
this concrete
* attempt (e.g., it can fail when topology is changing), but it won't
be lost anyway.


On Wed, Mar 1, 2017 at 10:14 PM, rishi007bansod <ri...@gmail.com>
wrote:

> Suppose autoflush frequency is 10000msec for ignite data streamer that put
> data into cache. Now if I query this cache, then will this query result
> also
> include data from data streamer buffer(which is not flushed into
> cache)?(whose flush frequency we have set to 10 sec)
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Effect-of-Autoflush-frequency-in-Ignite-
> Data-Streamer-tp10977.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Best regards,
Andrey V. Mashenkov