Correct. In unit tests we normally use IgniteDataStreamer.autoFlushFrequency(10) to decrease the flush period to 10ms.
Maybe try to do the same to discard a flushing problem – like Valentin suggested. *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Tue, Oct 13, 2015 at 8:56 PM, vkulichenko <[email protected]> wrote: > BTW, do you call IgniteDataStreamer.close() when there is more data to add? > You should do this to make sure all the data is flushed from the streamer's > buffers into the cache. If there are only several entries in your test, it > can be the reason why they don't end up in the persistence store. > > -Val > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Write-behind-with-data-streamer-tp1598p1605.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
