[
https://issues.apache.org/jira/browse/NIFI-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-16215.
-------------------------------------
Fix Version/s: 2.12.0
Resolution: Fixed
> ConnectionStatusEvents don't include current transaction enqueues
> -----------------------------------------------------------------
>
> Key: NIFI-16215
> URL: https://issues.apache.org/jira/browse/NIFI-16215
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Jakub Bogusz
> Assignee: Jakub Bogusz
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Example of an affected scenario:
> # producer enqueues 100 FlowFiles
> # event is emitted with queue size of 0 (due to bad operation ordering)
> # consumer consumes 100 FlowFiles within one transaction
> # Dequeues are counted correctly so event is emitted with queue size of 0
> In worst case scenario of a batch producer, batch consumer and low limit
> configured on the queue, we will always report an empty queue, while in
> reality it will be full most of the time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
