[
https://issues.apache.org/jira/browse/NIFI-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578237#comment-14578237
]
Michael Moser commented on NIFI-627:
------------------------------------
I think of 2 use cases for Control Rate. 1) When your data rate fluctuates,
you have limited WAN bandwidth, and you are willing to buffer data on your
system and delay its delivery, then ControlRate should be able to smooth the
rate that data is sent over the WAN and avoid saturating it during busy parts
of the day. 2) If you are feeding Splunk and have a license that limits how
much data you can ingest to it per day, then you can roughly control the rate
of ingest to Splunk. Of course in that scenario you must be willing to age off
buffered data if you are generating more than your license allows.
> 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
> Fix For: 0.2.0
>
>
> 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)
