Hi Valentin, I want to extend to job stealing collision in such a way that the maximum number of active jobs is defined based on the actual resources needed by the jobs (cpus, memory, storage).
For example, if a node has 60GB of memory and there are 10 pending jobs each of which need 10 GB to run, I want to executed only 6 of them and keep the others in the wait list. Currently the `JobStealingCollisionSpi` does not allow that. Instead of reimplementing it from scratch I was thinking to implement this logic in a custom collision SPI and delegate the job stealing mechanism to an instance of `JobStealingCollisionSpi`. Cheers, Paolo On Thu, Jan 28, 2016 at 11:20 PM, vkulichenko <[email protected] > wrote: > Hi Paolo, > > What's the use case? Why do you want to modify the collection before giving > it to the SPI? > > Thanks, > Valentin > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Is-it-safe-to-modify-the-activeJobs-and-waitingJobs-collections-in-the-CollisionContext-tp2758p2767.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
