Re: NiFi Wait / Notify not releasing on signal

(Forgot clicking the SEND button...) Hi ara, thank you for sharing the issue. I've submitted a PR to add new 'Penalize Waiting FlowFiles' property to Wait processor. https://github.com/apache/nifi/pull/3538/files To make existing flows intact, it's disabled by default. If enabled, FlowFiles rout

Re: NiFi Wait / Notify not releasing on signal

I see. Well, the good news is that it is easily replicated. If I queue up 2 FlowFiles, one with signal=aa, the other with signal=bb, then i use Notify to signal bb, the Wait processor does not process it. If I then Notify on signal aa, then both FlowFiles get processed by the Wait processor. Giv

Re: NiFi Wait / Notify not releasing on signal

I'm not going over 20,000 flowfiles, I have barely 2 in there. I just think thats how its coded. Somehow the FIFO can see all the items in the queue and no matter the signal can rip them out of any order, but the other Prioritizers bring one to the front of the queue and only consider that when m

Re: NiFi Wait / Notify not releasing on signal

Hello, I think what you are running into is NIFI-4460 [1]. The issue revolves around FlowFiles being swapped out. In order to avoid heap exhaustion, NiFi will "swap out" FlowFiles that reside in the queue. By default, this happens when you hit 20,000 FlowFiles in a queue. In that case, the Wait

Re: NiFi Wait / Notify not releasing on signal

I played around with the prioritizers some more and I can set 2 prioriters, PriorityAttributePrioritizer + FIFO, and then i can get the signal thats in the back of the queue , but its with a caveat, the priorities have to be the same. So with Queue having prioritizers: PriorityAttributePrioritiz

Re: NiFi Wait / Notify not releasing on signal

Here's the template, same as before but i've set prioritizer to PriorityAttributePrioritizer, and for my 2 flowfilegenerators updated to have attribute 'priority', and both have priority=2. https://pastebin.com/z5MWWaJL

Re: NiFi Wait / Notify not releasing on signal

Let me rephrase, I need to use PriorityAttributePrioritizer on the Wait queue. It seems to fail, meaning with flowfile1 (signal aa), and flowfile2 (signal bb) in the queue. I cannot send Notify signal=bb, and get the 2nd flowfile out, again it seems to be looking at the front of the queue. I

Re: NiFi Wait / Notify not releasing on signal

Not sure I follow, would probably have to see another template that shows what is not working. On Mon, Jun 17, 2019 at 3:52 PM ara m. wrote: > > Hey Bryan - Thank you ! you're absolutely right. Putting in FIFO totally > makes it work. > > My original issue was actually with prioritizer set to > P

Re: NiFi Wait / Notify not releasing on signal

Hey Bryan - Thank you ! you're absolutely right. Putting in FIFO totally makes it work. My original issue was actually with prioritizer set to PriorityAttrributePrioritizer, and using priority attribute, with differing values. For example if I had sent to Wait the following: signals aa (priority=

Re: NiFi Wait / Notify not releasing on signal

Hello, I think the issue is that wait relationship looped back to itself has no prioritizer configured on the queue. The flow file with ${signal} = aa is in the queue first, and each time it checks it and transfers back to wait, it happens to be put back in front of the one with bb. If you config

RE: NiFi Wait / Notify not releasing on signal

Here's the wait-notify-2-signal.xml - https://pastebin.com/uiBjm7qj And some screenshots of the flow and configs. You can see I have sent a flowfile with attribute ${signal}=aa and flowfile with ${signal}=bb, and my Wait relationship has 2 in the queue connection, which are my 2 signals. Then

RE: NiFi Wait / Notify not releasing on signal

ould be helpful. -Walter -Oorspronkelijk bericht- Van: ara m. [mailto:arama...@gmail.com] Verzonden: woensdag 12 juni 2019 22:39 Aan: users@nifi.apache.org Onderwerp: NiFi Wait / Notify not releasing on signal Hi guys, I've played around with Wait/ Notify extensively and something seems

NiFi Wait / Notify not releasing on signal

Hi guys, I've played around with Wait/ Notify extensively and something seems to be off. Unless I am wrong, it's either the documentation or behavior is off. Can somebody clear this up for me whether what I witness is correct behavior ? I have a Wait and Notify that are independent of each other,