Hi If you have a copy of the Camel in Action 2nd ed book, then we have a full chapter on clustering Camel that covers use-cases like this.
On Tue, Nov 21, 2017 at 1:07 PM, Zoran Regvart <[email protected]> wrote: > Hi Christine, > I think you need idempotent consumer pattern[1], with this you can > track in an external repository (multiple supported) what messages are > processed. There is also a nice tutorial on how to use this pattern > with Hazelcast[2] > > zoran > > [1] https://camel.apache.org/idempotent-consumer.html > [2] https://camel.apache.org/hazelcast-idempotent-repository-tutorial.html > > On Fri, Nov 17, 2017 at 4:34 AM, Christine Vladic > <[email protected]> wrote: >> Hi, >> >> I have a quartz camel service that invokes a REST API that returns a binary >> data. This service will be deployed in a clustered node thus multiple >> instances will invoke the same REST API and gets the same payload. >> Question, is there a camel pattern or component that can prevent instances >> of the same camel service processing the same data. >> >> Thank you, >> Chris > > > > -- > Zoran Regvart -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
