[
https://issues.apache.org/jira/browse/NIFI-12242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777839#comment-17777839
]
ASF subversion and git services commented on NIFI-12242:
--------------------------------------------------------
Commit 40ac38dfe3b12376050fd09f8017cea52bcb7943 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=40ac38dfe3 ]
NIFI-12242: Added ability to route data that exceeds the configured threshold
in ControlRate to be routed to 'rate exceeded' instead of just staying in the
queue. Added Use Case documentation to ControlRate.
This closes #7895
Signed-off-by: Mike Moser <mose...@apache.org>
> Allow ControlRate to optionally route to a new 'rate exceeded' relationship
> instead of just slowing things down
> ---------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-12242
> URL: https://issues.apache.org/jira/browse/NIFI-12242
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.latest
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> ControlRate provides the ability to slow down the rate of data through the
> system. This is important in cases where we want to avoid overwhelming a
> downstream system. However, there are times when we don't want to just slow
> down the flow of data but instead reject it if the rate is too high.
> Take, for example, the typical case with an HTTP Server that responds with a
> 429: Too Many Requests status code. ControlRate should give us the option of
> rejecting FlowFiles when they exceed the limit, not just slow everything down.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
