[ 
https://issues.apache.org/jira/browse/NIFI-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264697#comment-15264697
 ] 

ASF GitHub Bot commented on NIFI-1830:
--------------------------------------

GitHub user markap14 opened a pull request:

    https://github.com/apache/nifi/pull/394

    NIFI-1830: Fixed problems in the merging logic for Drop FlowFile Requests

    NIFI-1830: Fixed problems in the merging logic for Drop FlowFile Requests

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/markap14/nifi NIFI-1830

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/394.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #394
    
----
commit 0d9e66a4e356c34065c7afc59be931411f941221
Author: Mark Payne <[email protected]>
Date:   2016-04-29T20:07:37Z

    NIFI-1830: Fixed problems in the merging logic for Drop FlowFile Requests

----


> Empty Queue finishes before emptying all FlowFiles
> --------------------------------------------------
>
>                 Key: NIFI-1830
>                 URL: https://issues.apache.org/jira/browse/NIFI-1830
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>             Fix For: 1.0.0, 0.7.0
>
>
> When running a cluster, if there are a lot of FlowFiles in a queue, and a 
> user clicks "Empty Queue", it will drop a large percentage of them and then 
> the progress bar gets to 100% and it indicates that it is finished, having 
> dropped X number of FlowFiles, even though there are many FlowFiles still in 
> the queue. Subsequently choosing Empty Queue will indicate that 0 FlowFiles 
> were dropped but will drop some number of FlowFiles anyway, as is evidenced 
> by the size given on the connection after refreshing stats.



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

Reply via email to