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

["Mark Payne (JIRA)" <ji...@apache.org>]

Mark Payne created NIFI-5997:
--------------------------------

             Summary: If swap file written but FlowFile Repository fails to update, connection queue counts wrong and flowfiles are duplicated upon restart
                 Key: NIFI-5997
                 URL: https://issues.apache.org/jira/browse/NIFI-5997
             Project: Apache NiFi
          Issue Type: Bug
            Reporter: Mark Payne
            Assignee: Mark Payne
             Fix For: 1.9.0


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.



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