Re: Queue Prioritization

OK. The "GenerateFlowFile (on demand)" is only to "open the door" for the first time, next flowfile will release the next and so on, automatically. You can define any name for the release signal. I use "test.release" in this example. You have to use the same signal name in both Wait and Notify pro

Re: Queue Prioritization

Hi Eduardo, I have created the same flow in NIFI, the only thing I am not having is GenerateONDemand. and also am confused about how to set up the release signal for notifying and wait. Can you help me with that? On Mon, 2 Mar 2020 at 18:26, Eduardo Fontes wrote: > Sorry, > > Try this link: htt

Re: Queue Prioritization

Sorry, Try this link: https://pasteboard.co/IXejthc.png On Mon, Mar 2, 2020 at 9:35 AM Midhun Mohan wrote: > Hi Eduardo, > Can you please send the Image again, I am not able to open it > > On Mon, 2 Mar 2020 at 18:02, Eduardo Fontes > wrote: > > > Hi Midhun, > > > > I think this flow will do

Re: Queue Prioritization

Please upload it to somewhere and link it here. ASF mailing lists are striping the attachments/images. > On 2 Mar 2020, at 13:35, Midhun Mohan wrote: > > Hi Eduardo, > Can you please send the Image again, I am not able to open it > > On Mon, 2 Mar 2020 at 18:02, Eduardo Fontes

Re: Queue Prioritization

Hi Eduardo, Can you please send the Image again, I am not able to open it On Mon, 2 Mar 2020 at 18:02, Eduardo Fontes wrote: > Hi Midhun, > > I think this flow will do what you want. > > [image: image.png] > > Be advised that use of Wait/Notify will slow down the average throughput > of your fl

Re: Queue Prioritization

Hi Midhun, I think this flow will do what you want. [image: image.png] Be advised that use of Wait/Notify will slow down the average throughput of your flow because the aditional steps with the Cache. On Sun, Mar 1, 2020 at 12:57 PM Midhun Mohan wrote: > So I would like to know your sugges

Re: Queue Prioritization

So I would like to know your suggestions on how to implement wait and notify. In my case messages will flow one after another If a failure occurs I need to retry the failure before the orginal ones, and notify users if it fails again. On Sun, 1 Mar 2020, 6:31 pm Emanuel Oliveira, wrote: > Hi,

Re: Queue Prioritization

Hi, Invokehttp have 4 exits - success - error retry -> loop/count retries (updateattribite) -> if retries > max then logmessage(error) flow stops here ff discarded Otherwise loop back to invokehttp. - error type 2 (bad password etc, ) - error type 3 (connectivity problems) you may want also to lo

Re: Queue Prioritization

Hi my use case is When a invokehttp processor fails I need to stop the incoming message and retry the failed message 2 times and if it is success start the execution normally or if it fails again need to notify admins and stop the main invoke http processor. Hope you can get the scenario from t

Re: Queue Prioritization

Hi Midhun, You can use DistributedMapCacheServer which starts a cache service within NiFi's process, but I not recommend in production. Instead you could use RedisConnectionPoolService. To use solution Wait/Notify the NiFi must know the number of flowfiles to process in one queue before start ano

Re: Queue Prioritization

I think wait and notify can solve my problem. I checked the documents , which is bit unclear to me. Can anyone help me? Just to know few things like whether we need to configure a cache server, if so which one is best And also getting confused on how to configure wait and notify signals On Fri, 2

Re: Queue Prioritization

Hi! Maybe you should try another approach, like Wait/Notify or configure prioritizer just before the funnel, depending on your demand. On Fri, Feb 28, 2020 at 11:40 AM Midhun Mohan wrote: > Hi all, > How to prioritize one queue before a funnel? > > I need to make sure one queue is emptied befor

Queue Prioritization

Hi all, How to prioritize one queue before a funnel? I need to make sure one queue is emptied before another queue is taken over for executing, I tried with a priority attribute but it fails when a queue with less priority has messages before the queue with high priority. -- Regards, Midhun M

Re: Queue prioritization with backpressure

gt; > get > > > funneled into one processor. The connections use > OldestFirstPrioritizer, > > > and while there is no backpressure, the cross-queue prioritization > > appears > > > to work as designed (i.e., each queue that leads into the funnel > appears &g

Re: Queue prioritization with backpressure

tually > get > > funneled into one processor. The connections use OldestFirstPrioritizer, > > and while there is no backpressure, the cross-queue prioritization > appears > > to work as designed (i.e., each queue that leads into the funnel appears > to > > be fa

Re: Queue prioritization with backpressure

> In my flow, I receive flow files from multiple sources that eventually get > funneled into one processor. The connections use OldestFirstPrioritizer, > and while there is no backpressure, the cross-queue prioritization appears > to work as designed (i.e., each queue that leads into the fu

Queue prioritization with backpressure

In my flow, I receive flow files from multiple sources that eventually get funneled into one processor. The connections use OldestFirstPrioritizer, and while there is no backpressure, the cross-queue prioritization appears to work as designed (i.e., each queue that leads into the funnel appears