[
https://issues.apache.org/jira/browse/NIFI-16476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-16476.
-----------------------------------
Fix Version/s: 2.13.0
Resolution: Fixed
> Connection max queued duration reports 0 for clustered connections with empty
> partitions
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-16476
> URL: https://issues.apache.org/jira/browse/NIFI-16476
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Jakub Bogusz
> Assignee: Jakub Bogusz
> Priority: Minor
> Fix For: 2.13.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> On clustered nodes, connection max queued duration is often reported as 0
> even though FlowFiles are queued.
> SocketLoadBalancedFlowFileQueue.getMinLastQueueDate() treats the 0 returned
> by empty partitions as the oldest queue date. Non-load-balanced connections
> always have empty remote partitions, so they are affected most.
> SwappablePriorityQueue.getMinLastQueueDate() has the same flaw when the
> active queue is empty but the swap queue is not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
