You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2016/02/26 23:25:18 UTC

[jira] [Updated] (NIFI-1572) Empty Queue sometimes indicates that 0 FlowFiles were dropped, even when queue contains many FlowFiles

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

Mark Payne updated NIFI-1572:
-----------------------------
    Description: Specifically, we are seeing this with MergeContent as the target of the connection. It has about 1.2 million FlowFiles in its queue. The Processor was stopped. So the session should be rolled back. It is unclear if the problem is with rolling back the sessions or with Clearing the queue.

> Empty Queue sometimes indicates that 0 FlowFiles were dropped, even when queue contains many FlowFiles
> ------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-1572
>                 URL: https://issues.apache.org/jira/browse/NIFI-1572
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>             Fix For: 0.6.0
>
>
> Specifically, we are seeing this with MergeContent as the target of the connection. It has about 1.2 million FlowFiles in its queue. The Processor was stopped. So the session should be rolled back. It is unclear if the problem is with rolling back the sessions or with Clearing the queue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)