[jira] [Updated] (NIFI-12242) Allow ControlRate to optionally route to a new 'rate exceeded' relationship instead of just slowing things down

["Mark Payne (Jira)" <ji...@apache.org>]

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

Mark Payne updated NIFI-12242:
------------------------------
    Status: Patch Available  (was: Open)

> 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: 10m
>  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)