[NIFI-5997] If swap file written but FlowFile Repository fails to update, connection queue counts wrong and flowfiles are duplicated upon restart

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.8.0, 1.7.1
• Fix Version/s: 1.9.0
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 01/Feb/19 18:07
• Updated: 02/Apr/19 14:08
• Resolved: 05/Feb/19 20:24

Description

If a queue writes out a Swap File but then the FlowFile Repository throws an Exception when attempting to update, we end up with a scenario where the size of the queue increases by 10,000 FlowFiles (the number of FlowFiles to be written to the swap file) as well as the corresponding size of the FlowFiles. We also have a Swap File that is written out to disk but the FlowFile Repo didn't get updated so on restart we have those FlowFiles in the FlowFile Repo as well as in the Swap File, so we end up with two of the same FlowFile. This can then cause some odd behavior because two FlowFiles exist with the same ID and the counts on the queues are very wrong, which also causes a lot of confusion.

Issue Links

• links to: GitHub Pull Request #3290
• links to: GitHub Pull Request #3292