[ 
https://issues.apache.org/jira/browse/NIFI-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Percivall resolved NIFI-4874.
------------------------------------
    Resolution: Fixed

I believe this to be fixed as part of NIFI-3155

> RPGs to flows that share the same flow and port UUIDs can cause 
> non-deterministic FlowFile transmission
> -------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-4874
>                 URL: https://issues.apache.org/jira/browse/NIFI-4874
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Joseph Percivall
>            Priority: Major
>             Fix For: 1.5.0
>
>
> To replicate, set up three different 1.4.0 NiFi instances, one sender, and 
> two receivers. On one of the senders, create a simple flow consisting of a 
> single input port with a connection to a LogAttribute processor. Copy this 
> instance's flow.xml to the other receiving instance. Start the remaining 
> instances.
> On the sender, create a flow with a GenerateFlowFile to a Funnel which has 
> connections going to two RPGs (one for each receiver). With both RPGs having 
> disabled transmission generate a single FlowFile (leading to the queues in 
> front of each RPG with one).
> To be explicit, the receiving flows must be started from copies of the same 
> flow.xml (leading to the same port and flow UUIDs).
> Enable and disable transmission on one RPG. Notice the following:
> 1: The stats on both increases (NIFI-4571) 
> 2: Potentially, that the FlowFile was sent to the wrong instance.
> Repeat with the other RPG and as needed (since the issue is 
> non-deterministic). 
> This also appears to happen shortly after enabling both RPGs 
> (GenerateFlowFile stopped, enabled both RPGs, start/stop the GenerateFF 
> relatively quickly to see non-deterministic behavior).
>  
> This appears to have been fixed in 1.5.0 (I can't replicate) and I'm guessing 
> fixed with NIFI-3155. Logging this issue for explicit visibility of the bug 
> manifestation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to