Hi Yeah you can use idempotent read lock strategy and use the database idempotent repository, or implement your own.
The Camel in Action 2 book covers such an use case in the transaction chapter. And note that there is also idempotent-rename and idempotent-changed as strategies that combine the two of them (idempotent + xxx). Another approach would be to use a route policy and then control in the cluster so only 1 route is active at any given time, for example using zookeeper or something else. But then only one node in the cluster is processing the files. On Thu, Feb 9, 2017 at 10:28 AM, Laurentiu Trica <laurentiu.tr...@moredevs.ro> wrote: > Hi, > > You could implement your own lock strategy that should use a database to > give the lock to the first server that requires it and deny for all the > others. > > Good luck! > > On Thu, Feb 9, 2017 at 11:13 AM, garybarker <gary.bar...@first-utility.com> > wrote: > >> Is it possible to set up multiple servers connecting to the same remote >> SFTP >> server and guarantee that only one will consume each file there? A database >> backed idempotent table is the best way? >> >> Gary >> >> >> >> -- >> View this message in context: http://camel.465427.n5.nabble. >> com/Idempotent-SFTP-route-tp5793710.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > > > > -- > Laurentiu Trica > Software Developer Mobile: (+40) 722 329318 > S.C MoreDevs S.R.L. Email: laurentiu.tr...@moredevs.ro > > This message can contain privileged or confidential information and it is > intended only for addressee. Any unauthorized disclosure is strictly > prohibited. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
