ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrei Aleksandrov <aealexsand...@gmail.com>
Subject Re: Job Stealing node not stealing jobs
Date Tue, 03 Sep 2019 15:29:01 GMT

Some remarks about job stealing SPI:

1)You have some nodes that can proceed the tasks of some compute job.
2)Tasks will be executed in public thread pool by default:
3)If some node thread pool is busy then some task of compute job can be 
executed on other node.

In next cases it will not work:

1)In case if you choose specific node for your compute task
2)In case if you do affinity call (the same as above but node will be 
choose by affinity mapping)

According to your case:

It's not clear for me what exactly you try to do. Possible job stealing 
didn't work because of your weak node began executions of some tasks in 
public pool but just do it longer then faster one.

Could you please share your full reproducer for investigation?


9/3/2019 1:43 PM, Pascoe Scholle пишет:
> HI there,
> I have asked this question, however I asked it under a different and 
> resolved topic, so I posted the quest under a more suitable title. I 
> hope thats ok
> We have tried to configure two compute server nodes one of which is 
> running on a weaker machine. The node running on the more powerful 
> machine always finished its tasks far before
> the weaker node and then sits idle.
> The node is not even sending a steal request, so I must have 
> configured something wrong.
> I have attached the code for both nodes if you could kindly point out 
> what I am missing , I would really appreciate it!

View raw message