In a considerable manner, because the idea is to resize the cluster dynamically launching new grid nodes in order to steal jobs starving in waiting status.
In wondering if it is would be enough to remove this check: https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/spi/collision/jobstealing/JobStealingCollisionSpi.java#L734-L748 In that case would be so difficult, because I'm already taking in consideration to write my own collision strategy "cloning" the default one. Thanks for your help. Cheers, Paolo On Tue, Mar 1, 2016 at 10:28 PM, vkulichenko <[email protected]> wrote: > Paolo, > > So you're saying that jobs are not stolen by the node that joined after the > task is executed? I guess this is possible, because the task topology is > sealed during mapping phase. How critical is this for you? > > -Val > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Failed-to-send-message-tp3217p3311.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
