[NIFI-13281] Changing process group concurrency/outbound policy while data is within the group appears to result in stuck flow files

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.26.0, 2.0.0-M3
• Assignee: Mark Payne
• Reporter: Joe Witt
• Created: 21/May/24 22:25
• Updated: 10/Jun/24 20:58
• Resolved: 10/Jun/24 20:58

Description

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.

Issue Links

• duplicates: NIFI-13340 Flowfiles stopped to be ingested before a processor group