You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2014/12/07 03:56:12 UTC

[jira] [Updated] (NIFI-90) Replace explicit penalization with automatic penalization/back-off

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

Joseph Witt updated NIFI-90:
----------------------------
    Component/s: Core Framework

> Replace explicit penalization with automatic penalization/back-off
> ------------------------------------------------------------------
>
>                 Key: NIFI-90
>                 URL: https://issues.apache.org/jira/browse/NIFI-90
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Joseph Witt
>
> Rather than having users configure explicit penalization periods and requiring developers to implement it in their processors we can automate this.  Perhaps keep a LinkedHashMap<Connection ID, Counter> of size 5 or so in the FlowFileRecord construct.  When a FlowFile is routed to a Connection, the counter is incremented.  If the counter exceeds 3 visits to the same connection, the FlowFile will be automatically penalized.  This protects us "5 hops out" so that if we have something like DistributeLoad -> PostHTTP with failure looping back to DistributeLoad, we will still penalize when appropriate.
> In addition, we will remove the configuration option from the UI, setting the penalization period to some default such as 5 seconds.



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