Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

Hi Ryan, Yes, I think. But note that will create a high contention on this method - each job request will acquire the same lock. Although, it's probably not an issue in your case as you do not allow to execute more than one job at a time anyway. -Val -- View this message in context:

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

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:

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

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.

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

Interesting. I'll have to give that a try. The documentation for PublicThreadPoolSize explains that the executor service will be in charge of processing GridJobs and user messages set to the node. What are examples of user messages? Would that include usages of IgniteMessaging such as the

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

Ryan, I added a comment in the ticket. I would recommend you to set the size of public thread pool to 1 (IgniteConfiguration#publicThreadPoolSize) to make sure that jobs are not executed in parallel. -Val -- View this message in context:

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

Hi Ryan, I will take a look this week. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Concurrent-job-execution-and-FifoQueueCollisionSpi-parallelJobsNumber-1-tp8697p13440.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

I used the previously provided example and duplicated the issue in the Ignite 2.0 release on Windows 10 I also created an issue: IGNITE-5183 On 4/12/2017 2:15 PM, Ryan Ripken wrote: I tried the below example with Ignite 1.9 and I continue

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

Please let me know if I can help in any way. On 4/13/2017 2:18 AM, vkulichenko wrote: Hi Ryan, I will take a look at your sample in the next few days. -Val -- View this message in context:

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

Hi Ryan, I will take a look at your sample in the next few days. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Concurrent-job-execution-and-FifoQueueCollisionSpi-parallelJobsNumber-1-tp8697p11935.html Sent from the Apache Ignite Users mailing list

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

Ignite Team - I created a stripped down version of what I'm trying to do: https://www.dropbox.com/s/zhxidn14cgi4dqg/IgniteTest.7z?dl=0 There are a couple variables in node.bat that will need to be edited to point at your java_home and to the path where the 7z is unzipped to. I first start a

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

The issue seemed weird to me as well. It was not reproducible and so I just assumed that something must have gone wrong with the installation. I had this issue occur in January and it just happened again over the weekend. This was using Ignite 1.5.0.final. I've verified that all the nodes

Re: Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

Collision SPI is called on the node that executes the job. Having said that, what you tell sounds a bit weird. Are you sure other nodes didn't lose the config as well? -Val -- View this message in context:

Concurrent job execution and FifoQueueCollisionSpi.parallelJobsNumber=1

Can different nodes have different collisionSpi settings? What setting would take effect - the collisionSpi used to start the grid or the setting on the node executing the job or the setting on the node that submitted the task? I recently encountered a log file that could only have been