Adding log in text. Looks like the image didn’t go through. 2023-09-26 08:16:58,207 DEBUG [Timer-Driven Process Thread-7] o.a.nifi.amqp.processors.ConsumeAMQP ConsumeAMQP[id=78f68d05-f59d-3b9b-746e-5d480be723df] has chosen to yield its resources; will not be scheduled to run again for 1000 milliseconds 2023-09-26 08:16:58,207 DEBUG [Timer-Driven Process Thread-9] o.a.nifi.amqp.processors.ConsumeAMQP ConsumeAMQP[id=85c40dd5-3f41-3895-25e9-ee3569331185] has chosen to yield its resources; will not be scheduled to run again for 1000 milliseconds
Ivan Dolinin / (416) 583-5833 x2012 / [email protected]<mailto:[email protected]> From: Ivan Dolinin <[email protected]> Sent: Tuesday, September 26, 2023 12:20 PM To: Joe Witt <[email protected]>; [email protected] Subject: RE: Processor stuck in yielding Joe, thank you for a very quick response. Here is the screenshot of the log. There is nothing else recorded for the UUID 78f68d05-f59d-3b9b-746e-5d480be723df. I could not trace the beginning of this s External ([email protected]<mailto:[email protected]>) Report This Email<https://protection.inkyphishfence.com/report?id=c2tvdXQtY2xldmVyLWRldmljZXMvaWRvbGluaW5AY2xldmVyZGV2aWNlcy5jb20vYTlhNmI0NTdkZjI1MTJkY2IxMDk1YWEwOWRhODFmNzcvMTY5NTc0NTIyMS41MQ==#key=f2570b6645b6fccfecd3bdb17740f48a> FAQ<https://getskout.com/emailprotectionfaq/> Skout Email Protection<https://getskout.com/emailprotection/> Joe, thank you for a very quick response. Here is the screenshot of the log. There is nothing else recorded for the UUID 78f68d05-f59d-3b9b-746e-5d480be723df. I could not trace the beginning of this state. We have 3 ConsumeAMQP processors reading from RabbitMQ, only this one is yielding, other 2 reading messages as expected. [cid:[email protected]] Ivan Dolinin / (416) 583-5833 x2012 / [email protected]<mailto:[email protected]> From: Joe Witt <[email protected]<mailto:[email protected]>> Sent: Tuesday, September 26, 2023 11:49 AM To: [email protected]<mailto:[email protected]> Subject: Re: Processor stuck in yielding Ivan, Please show what the logs state specifically if you can. That processor could yield for the following reasons from a quick look: 1. The connection between it and the next processor in the flow is a full queue not being processed fast enough. 2. The data connection to AMQP is working but it is told there is no data currently to pull. 3. ... That is about it actually. I am looking at the current code though. NiFi 1.8.0 is 5 years old (today ironically) and that processor and the associated libraries and even framework have changed a lot since then. You will definitely need to try your flow on the latest 1.23.x line if the issue being seen is not a simple config problem. Thanks On Tue, Sep 26, 2023 at 8:40 AM Ivan Dolinin <[email protected]<mailto:[email protected]>> wrote: Hello, In one of our production instances running NiFi 1.8.0, the ConsumeAMQP processor is stuck in yielding. All the log is saying that it has chosen to yield. No errors are happening in the downstream processors. There are thousands of messages in the queue it is reading from. The processor is connecting to the queue. What could be the reason? Thanks, Ivan Dolinin
