On Tue, Mar 19, 2013 at 12:34 PM, yogu13 <yogesh....@synechron.com> wrote: > Hi Claus, > > Can you let us know what do you mean by "Though an alternative is to use a > shared idempotent repository that the ftp consumer can use. That is a bit > special as the file/ftp consumer has this functionality built-in" >
Yeah this allows you to have all nodes in the cluster be active and try to pickup FTP files. And with a shared idempotent repository configured on them, this can ensure a file is only being picked up by a single node. Where as the "Camel cluster" using quartz, hazelcast etc. is using a strategy of one node being a master, and the others slaves. And when the master dies, one of the slaves become the new master etc. But then there is only one active node running. > As mentioned will try to search the discussion group as well on clustered > camel. > > Thank you! > > Regards, > -Yogesh > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-FTP-component-on-cluster-tp5729403p5729407.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
