Hello! It just sounds that you want to prioritize some other resource rather than Ignite compute capacity, if you want cluster-wide priorities.
This means that Ignite prioritizing is a poor fit for you and you may need to roll out your own, perhaps based on IgniteQueue. Regards, -- Ilya Kasnacheev вс, 16 мая 2021 г. в 13:20, Krish <kishanthesiy...@gmail.com>: > Thanks Stephen and Ilya, > > As mentioned in job scheduling documentation, collisionAPI will take care > of > job scheduling when jobs arrive at destination node. Lets say I use > PriorityQueueCollisionSpi and send three jobs with priorities 5, 7 and 10 > to > one node, then that node will execute job with priority 10 first then job > with priority 7 and then 5. > > However, My use case is different than this. Going with above example, in > my > use case, ignite client will send three jobs to three different nodes and I > would still want these jobs to be executed based on their priorities. > Basically, no matter how these jobs are distributed across the cluster they > should be executed based on priority. Can this be achieved using > CollisionAPI? > > Many Thanks, > K > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
