Hello! Just make sure to use new PriorityQueueCollisionSpi().setStarvationPreventionEnabled(false);
otherwise you may get sorting errors on newer JVMs. Regards, -- Ilya Kasnacheev чт, 13 мая 2021 г. в 11:31, Stephen Darlington < stephen.darling...@gridgain.com>: > Yes, it’s configurable using the CollisionSPI. More here: > https://ignite.apache.org/docs/latest/distributed-computing/job-scheduling > > Regards, > Stephen > > > On 13 May 2021, at 06:39, Kishan <kishanthesiy...@gmail.com> wrote: > > > > Hi All, > > > > I have a use case I need to create 1000s of ignite Callable tasks and > > execute these tasks on ignite cluster. Some of these jobs should be > executed > > on high priority by ignite cluster. For example, ignite client has sent > > around 50 tasks to cluster and now they are in queue or are being > executed. > > At this point, client receives a request which should be executed with > > highest priority. Client will create a compute task with priority set to > > High and send it to ignite cluster via executor service. Is there any way > > ignite can know that certain tasks which are are submitted with high > > priority should be executed before any other tasks present in the queue? > > > > Thanks.. > > K > > > > > > > > -- > > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > >
