[
https://issues.apache.org/jira/browse/NIFI-10353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579725#comment-17579725
]
Peter Schmitzer commented on NIFI-10353:
----------------------------------------
Hi guys, we are using an azure eventhub as a central input source for our data
ingestion and thus have the ConsumeAzureEventHub processor in place. Our idea
was in case of outages of downstream systems that we can use the backpressure
mechanisms of the nifi queues to have all queues backpressured up to the azure
eventhub itself and then basically have nifi to "stop processing". All the new
messages will wait in the eventhub for us.
Unfortunately, that does not happen and it behaves as described above.
> ConsumeAzureEventHub does not stop even though output queue is backpressured
> -----------------------------------------------------------------------------
>
> Key: NIFI-10353
> URL: https://issues.apache.org/jira/browse/NIFI-10353
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.16.3
> Reporter: Peter Schmitzer
> Priority: Major
>
> ConsumeAzureEventHub seems to not care about backpressure and continues to
> send flowfiles to the output queue even though it is backpressured. This
> endlessly growing queue will ultimately lead to nifi going into overload and
> be unhealthy.
> It was expected that the processor will stop putting further data in the
> outgoing queue as soon as it is backpressured.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
