[
https://issues.apache.org/jira/browse/NIFI-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732875#comment-16732875
]
ASF subversion and git services commented on NIFI-5919:
-------------------------------------------------------
Commit fea17d0ca875d2450c21b69dc0c6c241374834e5 in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=fea17d0 ]
NIFI-5919: Addressed a race condition that can exist if adding FlowFiles to a
FlowFileQueue before adjusting the size of the queue to account for the
FlowFiles
Signed-off-by: Pierre Villard <[email protected]>
This closes #3238.
> Occasionally FlowFiles appear to get "stuck" in a Load-Balanced Connection
> --------------------------------------------------------------------------
>
> Key: NIFI-5919
> URL: https://issues.apache.org/jira/browse/NIFI-5919
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a Connection is configured to Load Balance across the cluster, we have
> seen reports on the mailing list of FlowFiles getting "stuck". The connection
> shows that the data is being actively load balanced, but the FlowFiles never
> move. Listing or emptying the queue indicate that there are no FlowFiles.
> Upon restart, the FlowFile does not exist and the queue is cleared.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
