Raul,
/If I understand correctly, flushing controls when the changes in the
streamer will be sent to the grid (can someone confirm?). /
Your understanding is correct. Autoflush allows to trigger data flushing
to the grid periodically.
If autoflush is disabled then the data is sent either when
IgniteDataStreamer. perNodeBufferSize is reached or flush()/close() is
called manually.
--
Denis
On 3/20/2016 1:12 PM, Raul Kripalani wrote:
Auto flush / flushing is a characteristic of all streamers, that's why
you won't find it explained explicitly in the docs of specific
streamers, but in the general streamer one.
If I understand correctly, flushing controls when the changes in the
streamer will be sent to the grid (can someone confirm?).
Autoflush is disabled by default, i.e. meaning that you must call
flush() manually on the streamer for the writes to be visible in the
cache.
To avoid that, and if your use case permits it, autoflush will flush
the buffered entries periodically.
When in doubt, you can check the unit tests for the component you're
working with.
Cheers,
Raúl.
On 20 Mar 2016 02:02, "techbysample" <[email protected]
<mailto:[email protected]>> wrote:
That worked. Thank you very much.
Would you please elaborate on how property is used?
Does it imply that by default autoflushFrequency is disabled and
DataStreamer will NOT
write data to cache unless explicitly set?
I basically modeled my JMSStreamer after the following
documentation here:
https://apacheignite.readme.io/docs/jms-data-streamer
The docs do not explicitly mention setting 'autoflushFrequency'..
Here is definition from Apache Ignite docs: -
dataStreamer.autoFlushFrequency:
"Sets 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.
If set to 0, automatic flush is disabled.
Automatic flush is disabled by default (default value is 0)."
Please advise.
Thank you
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/JMS-Data-Streamer-Not-writing-data-to-cache-when-message-received-by-Streamer-tp3590p3592.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.