Hi! We had a similar problem when using "parallel processing" on a single machine and searched for a solution without using aggregator or sequencer. At the very end we sent the results processed in parallel back to a common "ack" queue (maybe you strip the body before) which runs in the same process as the splitter. You can now simply check the inflight repo for pending messages. Split-index won't work as the split-complete message may arrive out-of-sequence.
Jens Von meinem iPhone gesendet > Am 04.07.2015 um 18:46 schrieb camelstarter <[email protected]>: > > Hello, > > when splitting big file while distributing the work on multiple machines, > I'm facing the problem not knowing, when the file is completed. The only > idea I have, is to use database for logging the errors and processed units > and always check, whether the sum of errors and processed lines equals total > number of lines. Is there a better way to do it? > > from(file) > .split() > .streaming().to(queue); > > > from(queue) > .process(processor) > .process(DbLogger); > > > Thanks in advance! > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/knowing-wenn-splitted-exchange-is-completed-in-distributed-env-tp5768880.html > Sent from the Camel - Users mailing list archive at Nabble.com.
