Hi all, I personally think this is a good candidate for implementing Ignite Queue Based messaging where any one of the given nodes can pick up the message. Upon task completion it should fire an event which should be picked up by any node just the way jms queue works. However I am not sure whether we could achieve the same functionality with topic based messaging or not, but then I can think of cases where it will not work and needs to be handled by clients
I also agree with what Val said as well which is definitely something missing from the computation API. [+1] Other solution would be is to implement some kind of event bus at the cache level which is able to register user related events in a specific order and function definitions can be implemented respectively on the listener side. Upon the completion of a task user should fire an event on that event bus - the only difference between this and ignite topic based messaging would be that upon firing the event it will select a random node on which the message will be deliver, which guarantees that the message is delivered one and only once to one random node. I know we have already got so many ignite events but 1. they are not reliable 2. we already so many events going inside the ignite, so would drop it. - Luqman -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Tasks-Scheduling-and-Chaining-tp14293p14558.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
