Hello, Yes, it's guaranteed that only one node will take each distinct value from the IgniteQueue. https://apacheignite.readme.io/docs/queue-and-set#section-cache-queues-and-load-balancing
On Tue, Mar 21, 2017 at 10:00 PM, kmandalas < [email protected]> wrote: > Hello Alex and thanks for the reply. > > i am checking the links you sent. If I do follow the IgniteQueue approach > to > put tasks in a distributed queue and have nodes take them for execution, am > I absolutely covered that only one grid node will take an item-task from > the > queue? From the example I see, we use broadcast() passing data and > callables > to notify all nodes that an item has been placed in the queue. Then each > node, upon receiving the broadcast message, the callable it will run will > attempt to take an item from the queue and do some work on it. I suppose > that since IgniteQueue is thread-safe and all, then there won't be any > issue. > > Please for your opinion. > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Cache-Queues-and-Load-Balancing-tp11223p11345.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Kind regards, Alex.
