Thank you very much. Will give it a shot and let you know of any issues.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/DataStreamer-pool-tp5857p8320.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Meant to say Partitioned cache. Sorry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/DataStreamer-pool-tp5857p8203.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
to use the
data streamers. putAll is way too small. The cache is a replicated cache
with one back up. Thank you.
Tarek
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/DataStreamer-pool-tp5857p8189.html
Sent from the Apache Ignite Users mailing list archive
Hi Dmitriy,
I would simply start the streaming in a separate thread right after the compute
task is received. If you need to send a result to the compute task’s originator
after the streaming has finished you can use Ignite Continuation functionality
releasing a thread from the public pool
Hi igniters!
Using data streamer from compute tasks may cause starvation, because
both operations are executed in the same public pool. Is it possible to
add configuration for separate thread pool for data streamer?
Thanks!
Dmitry.
