Re: Retry on HTTP processor preserving order of flow file

Thank you for your thoughts on it. Eduardo On Wed, 29 Jul 2020 at 06:00, Eduardo Fontes wrote: > Hi Midhun, > > Good idea! This way the processor will not consume from the main input > connection because at least one of its output connection's queue is full, > but it can consume from the

Re: Retry on HTTP processor preserving order of flow file

Hi Midhun, Good idea! This way the processor will not consume from the main input connection because at least one of its output connection's queue is full, but it can consume from the "failure" because it will release the queue. Good job! On Mon, Jul 20, 2020 at 12:57 PM Midhun Mohan wrote: >

Re: Retry on HTTP processor preserving order of flow file

Hi Eduardo, Thanks for the suggestions, I finally ended up testing it in a different way. 1. Having the failure/retry relationship connected back to invoke http processor with a backpressure value as 1. 2. So on any failure all messages will get queued up before the invokehttp processor. 3. When

Re: Retry on HTTP processor preserving order of flow file

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

Re: Retry on HTTP processor preserving order of flow file

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 wrote: > Hi Mithun, > > First of all, did you verify if the sequence

Re: Retry on HTTP processor preserving order of flow file

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

Retry on HTTP processor preserving order of flow file

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