Joe Witt created NIFI-13281:
-------------------------------
Summary: Changing process group concurrency/outbound policy while
data is within the group appears to result in stuck flow files
Key: NIFI-13281
URL: https://issues.apache.org/jira/browse/NIFI-13281
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 2.0.0-M3, 1.26.0
Reporter: Joe Witt
Attachments: DATFLOW_TO_REPRODUCE_ISSUE.json
Ravinarayan Singh on slack shared the attached flow. And the described steps
Step to reproduce:
1. Upload the attached Flow
2. Start the flow
3. Stop the Flow and Configure the TEST processor with following:
Process Group FlowFile Concurrency: Single FlowFile Per Node
Process Group Outbound Policy: Batch Output
3. Start the flow ,Now flow file will be stuck
I just did the same process on the latest codebase and I do see the behavior.
I tried using a different sequence of steps such as
1. Upload attached flow
2. Stop the Flow and Configure the TEST processor with following:
Process Group FlowFile Concurrency: Single FlowFile Per Node
Process Group Outbound Policy: Batch Output
3. Start the Flow
4. Stop the flow
5. start the flow
And that sequence worked fine. So I am thinking what happens is that changing
concurrency/outbound policy when the flow is stopped but has data in it leads
to a weird condition possibly that then results in stuck flow files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
