You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Michael Moser (JIRA)" <ji...@apache.org> on 2016/02/05 22:47:39 UTC

[jira] [Commented] (NIFI-627) ControlRate processor does not accurately control the rate

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

Michael Moser commented on NIFI-627:
------------------------------------

[~aldrin] I would be happy to take this on for 0.6.0 if you like.  I would also include fixes for the bugs mentioned in NIFI-990 and NIFI-1329.

> ControlRate processor does not accurately control the rate
> ----------------------------------------------------------
>
>                 Key: NIFI-627
>                 URL: https://issues.apache.org/jira/browse/NIFI-627
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 0.1.0
>            Reporter: Michael Moser
>            Assignee: Aldrin Piri
>            Priority: Minor
>
> Set a ControlRate processor to something like 5 KB per 1 sec.  Generate flow files that are about 300 KB in size and feed a bunch to this processor.  This should allow about 5 files through per 5 minutes.  But it allows a lot more data through than it should.  The difference seems to get worse with really low Time Duration values.  And people tend to think in number of bytes per second so the temptation to set Time Duration to 1 sec is great.
> Also, if ControlRate has multiple input queues, it seems to output even more data than it should.
> This seems to be caused by the code at the beginning of ControlRate onTrigger().  Under some conditions when the number of files that are allowed through per Time Duration is less than 1, the Throttle is being removed from the throttleMap while it actually still should be in use.



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