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 <idoli...@cleverdevices.com.invalid> 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 > >
