Hi Midhu, I can't think in other solution that guarantees the order using only NiFi. Even if you put a funnel before the InvokeHTTP, receiving the main input and the retries with prioritizers in the queue, the order could not be guaranteed.Using other tools, you can do it by, for exemple, using an external queue (like Kafka), you could consume from it every time the InvokeHTTP succeed or failed with retries.
Eduardo Fontes Data Engineer On Fri, Jul 3, 2020 at 12:53 AM Midhun Mohan <midhun.mo...@esginc.us> wrote: > Hi Eduardo, > > It seems success on 100% success scenario, but 50 % failure scenario it > seems to be mixing up the sequence.. So do you have any other suggestion > than using wait/notify . > > On Wed, 1 Jul 2020 at 05:53, Eduardo Fontes <eduardo.fon...@gmail.com> > wrote: > > > Hi Mithun, > > > > First of all, did you verify if the sequence is ok in a 100% success > > scenario? If not, you could use the prioritizers to correct this. > > If you need to confirm every HTTP call (including retries) before process > > the next in the queue, you could use a Wait/Notify. But be advised that > > this approach will slow down the throughput of your flow. > > > > Eduardo Fontes > > Data Engineer > > > > > > On Tue, Jun 30, 2020 at 8:58 AM Midhun Mohan <midhun.mo...@esginc.us> > > wrote: > > > > > Hi all, > > > > > > I was trying to figure out a way to do a retry on http processor on > > > following scenario > > > > > > 1. The flow file should preserve the order , since the order of data is > > > critical for the API > > > > > > > > > I am using the retry processor to do the 3 times default retry with 20 > > sec > > > delay. All the In and Out queue is first in first out priority. > > > > > > > > > But on my realtime load test it seems the Order is not preserved. I am > > > getting a mix of responses. > > > > > > Please help me to figure it out > > > > > > > > > Thanks in advance > > > > > > -- > > > > > > > > > Regards, > > > Midhun Mohan > > > > > > > > -- > > > Regards, > Midhun Mohan >
