I use IgniteMessaging to update status info from inside my compute jobs
so publicThreadPoolSize=1 probably isn't going to work.
In your opinion, would a new CollisionSpi implementation that
synchronized the onCollision method resolve the issue?
On 6/9/2017 5:01 PM, vkulichenko wrote:
Ryan,
Yes, this is about IgniteMessaging API.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Concurrent-job-execution-and-FifoQueueCollisionSpi-parallelJobsNumber-1-tp8697p13586.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
